I only did 9 month not conding in android natively, I was using flutter meanwhile, and recently I had to get back to android native because a project need to be build in android natively using java to support a large version of android, so I needed to catch up and I can tell native android is a mess everything changes so fast and everywhere, when you all are saying it easy to do 😵💫😵💫 😵
I know that any major changes can't be commented on or spoken about but my main question is that we are now or will be with Android 15, year 4 of the Android 12 redesign that took place. A lot of changes that have since taken place have been more refinements and yes we've add many user facing features added since but the general design and functionality of core Android has not changed. Are you able to divulge any details for what we can expect with Android 16 next year, if we will see any core design changes, maybe not on the level of a Android 12 but I'm just wanting to know if this current Material You design framework will continue on for the time being. Thank you in advance.
Try reading those gibberish, less-detailed documentation of iOS/MacOS. No, don't clump Apple's documentation to the likes of Swift. Swift documentation is awesome, their language forum as well. Been trying to get into iOS for the last year and man, documentation is night and day. Android has a LOT better detail.
Also, my workplace still needs to support iOS 12, for some reason. Do you know what they do? They simply ignore all the advancements made in iOS 13, 14 and 17. Most of them don't even know what an Actor is (Swift Actor I mean). I know, not the best workplace but, I imagine there are similar workplaces like mine as well. They won't get affected by new changes simply because they don't know it exists in the first place! Some important changes DO break some existing implementations in older iOS.
navigation button transperancy is a bug of future 😂. where people can't use those transport part because of navigation button panel.. currently I'm facing this in somr games and video players.. rip
2:24 Edge-to-edge: How do I set the color to be primary-dark as before, for the status bar, along with white colors for the icons? What happens if I don't have AppBarLayout or CoordinatorLayout? 4:09 Predictive-back is still buggy, as the support library can't handle it properly. I've reported about this a long time ago and still nobody fixed it. Also there is sadly no way to tell it to use the same animation as of the OS , and the idea itself is weird when using navigation-component when the Fragments don't take the entire screen, as the animation won't take the entire screen. I also can't see how to have the predictive-back-gesture show what's behind for the navigation component. It seems to work only for apps with multiple-Activities, between them... Also how come the navigation component still can't have an animation set for all actions by default, and we have to set it per each action (the one that is from one Fragment to another) ? Or do we? The docs doesn't say. It only mentions it for a single action... 18:58 Privacy - still no permission for fetching the current wallpaper, so apps still need the MANAGE_EXTERNAL_STORAGE permission and even the READ_MEDIA_IMAGES together with it on some devices...
Not all aps on iOS are edge to edge, although most are. It's the same on android some apps are some aren't. But on android 15 it is the default for all apps to be edge to edge
Drop the "AI". Web HID needs to be built into Android. Android Studio needs to be native to Android. I should be able to plug my Z Fold into my monitor and use Android Studio in Samsung DeX. Necessitating the use of a non-native OS to develop an Android app is silly in this day and age. *Require* apps to support freeform windows and split-screen. Android desktop modes, tablets and foldables should be well supported. *Require* apps to support mouse and keyboard inputs. *Require* apps to support large screen UI dependent on viewport size rather than orientation. Portrait style foldables should display the large screen UI when unfolded without needing to rotate the device, especially now that the Pixel 9 Fold is a portrait style foldable. Better support large volumes of RAM but not killing and restarting apps like its still 2005. Phones should be able to retain active sessions and applications in RAM like any PC can without the worry of refocusing the app.only to have it reload your session.
Uhh, PC is no better in retaining active session in a RAM-constrained environment. They simply unload it to storage. Ever tried using up all your RAM capacity and Windows tries to load it from HDD? Yes, it happens back then. Also, some apps cleverly used the lifecycle callback to make sure that even if the app process got terminated by the system, the user can go back to where they were before. Some games I play like Genshin Impact do that. It still forces me to relogin but, full asset reloading is not needed.
@@kamikakushi_ uhhh, this isn't about "using up" RAM or a "RAM-constrained environment," it's about Android not effectively managing large volumes (e.g. 12GB and above). Devices routinely kill sessions long before using more than 75% of RAM. You have to perform convoluted gymnastics to get a 12GB device to even use more than 8GB.
@@nickthaskater So, where do you get this hard limit of 75% from? I can't seem to find it. Also, what's the use case of having to use more than 3-4GB of RAM per application?
@@kamikakushi_ I did not say anything about a hard limit. This is not about "3-4GB per application," either. It's about Android's aggressive tendency to kick applications out of RAM despite having plenty of headroom, without offloading the session to storage. For example, it's impossible to maintain an active, authenticated Citrix remote desktop session in the browser. If you minimize it momentarily to check another application, the session restarts and you need to reauthenticate and start all over again. As for a use case for more than 3-4GB per app, photo editing applications like Lightroom and video editing applications like LumaFusion, let alone web browsers, can all push that limit.
@@nickthaskater Ah, after reading the android source documentation, some old forums here and there and piece it together, I finally understand about what you wrote. Sorry if my reply might imply a snide remarks to your suggestions. Do you think it would be better if we have access to APIs that could make us developers able to understand what's going on behind the curtain with the kernel swap daemon or the low memory killer so that we could develop an app that could react accordingly? Kind of like onTrimMemory() but more granular.
Does Android have a future? I don't think so. There are always a lot of changes, which cause headaches for developers. Moreover, there are many restrictions for publishing apps on the Play Store. I've quit Android development, and now I'm happy with web development. Google is driving away Android developers.
AFAIK, web development has a much faster changes (i.e. in toolings, languages, important frameworks). Maybe time has changed but, I still prefer the slower tooling changes in mobile development. Also, Apple put many restrictions as well in their App Store. Google and Apple both do that for a very valid reason. Security and stability.
Yeah man, because everyone knows RUclips comments are where the best tech jobs are hiding. Try Google or, you know, an actual job site. But hey, maybe your future boss is just waiting here for the perfect comment!
The changes are not that hard to be made. It's not like you have to rework the implementation of OpenSL ES to Oboe or worse, manual support of AAudio It's similar to how programmatical UIKit of iOS does as well. Yes, it's what iOS have been doing for years.
Android 15 #AskAndroid → goo.gle/android15-ama
Yb😮gb CT se baat🪞🎀🎀😝🎀😝🎀🎀🎀😝✨🎀
This was one of the most informative and well done videos I have ever seen on this channel.
Love Google for their transparent approach and innovations, nowadays android is enhancing at greater pace thanks to the team 👏🏼
great dan and ash do more vids
Edge-to-edge is the biggest thing to come to Android since gesture navigation, and only then will this navigation mode be complete.
For the love of lord pls force every app to go edge-to-edge. iOS apps look so much better cuz they're immersive.
This is something that developers have to do, and it's very hard to do for Android because there are so many devices
This is coming. Next year it will be edge to edge with opt out. And maybe the year after no more opt out.
@@victorsamuellopezWell some phones you can force "Full screen" and they look native.
We use Android ❤
You can keep the AI
Android ❤❤❤
Handling insets in Flutter only require a single "SafeArea" widget.
What a mess.. Ppl who took over after Android 5 don't know what they're doing..
This is really rich, thanks
I only did 9 month not conding in android natively, I was using flutter meanwhile, and recently I had to get back to android native because a project need to be build in android natively using java to support a large version of android, so I needed to catch up and I can tell native android is a mess everything changes so fast and everywhere, when you all are saying it easy to do 😵💫😵💫 😵
I know that any major changes can't be commented on or spoken about but my main question is that we are now or will be with Android 15, year 4 of the Android 12 redesign that took place. A lot of changes that have since taken place have been more refinements and yes we've add many user facing features added since but the general design and functionality of core Android has not changed.
Are you able to divulge any details for what we can expect with Android 16 next year, if we will see any core design changes, maybe not on the level of a Android 12 but I'm just wanting to know if this current Material You design framework will continue on for the time being. Thank you in advance.
Every year you make the Android developer life harder. Anyone agree?
In iOS even they introduce new features, it will not affect the iOS developers.
Try reading those gibberish, less-detailed documentation of iOS/MacOS.
No, don't clump Apple's documentation to the likes of Swift. Swift documentation is awesome, their language forum as well.
Been trying to get into iOS for the last year and man, documentation is night and day. Android has a LOT better detail.
Also, my workplace still needs to support iOS 12, for some reason.
Do you know what they do? They simply ignore all the advancements made in iOS 13, 14 and 17.
Most of them don't even know what an Actor is (Swift Actor I mean).
I know, not the best workplace but, I imagine there are similar workplaces like mine as well.
They won't get affected by new changes simply because they don't know it exists in the first place!
Some important changes DO break some existing implementations in older iOS.
💯 so sick of supporting existing mission critical apps.
navigation button transperancy is a bug of future 😂. where people can't use those transport part because of navigation button panel.. currently I'm facing this in somr games and video players.. rip
Nice!
Shared element transitions in flutter require a single "Hero" widget. I can't believe how complex it is in Android.
Very nice
very nice
2:24 Edge-to-edge: How do I set the color to be primary-dark as before, for the status bar, along with white colors for the icons? What happens if I don't have AppBarLayout or CoordinatorLayout?
4:09 Predictive-back is still buggy, as the support library can't handle it properly. I've reported about this a long time ago and still nobody fixed it. Also there is sadly no way to tell it to use the same animation as of the OS , and the idea itself is weird when using navigation-component when the Fragments don't take the entire screen, as the animation won't take the entire screen.
I also can't see how to have the predictive-back-gesture show what's behind for the navigation component. It seems to work only for apps with multiple-Activities, between them...
Also how come the navigation component still can't have an animation set for all actions by default, and we have to set it per each action (the one that is from one Fragment to another) ? Or do we? The docs doesn't say. It only mentions it for a single action...
18:58 Privacy - still no permission for fetching the current wallpaper, so apps still need the MANAGE_EXTERNAL_STORAGE permission and even the READ_MEDIA_IMAGES together with it on some devices...
How did iOS have edge-to-edge since iPhone X without any issues or UI compatibility issue unlike android?
Not all aps on iOS are edge to edge, although most are. It's the same on android some apps are some aren't. But on android 15 it is the default for all apps to be edge to edge
Where can we get Dan's shirt from?
Hey Are sharedtransition enabled for Compose Multiplatform?
Is Predictive Back cross platform? Can I use it in my compose multiplatform project?
Drop the "AI".
Web HID needs to be built into Android.
Android Studio needs to be native to Android. I should be able to plug my Z Fold into my monitor and use Android Studio in Samsung DeX. Necessitating the use of a non-native OS to develop an Android app is silly in this day and age.
*Require* apps to support freeform windows and split-screen. Android desktop modes, tablets and foldables should be well supported.
*Require* apps to support mouse and keyboard inputs.
*Require* apps to support large screen UI dependent on viewport size rather than orientation. Portrait style foldables should display the large screen UI when unfolded without needing to rotate the device, especially now that the Pixel 9 Fold is a portrait style foldable.
Better support large volumes of RAM but not killing and restarting apps like its still 2005. Phones should be able to retain active sessions and applications in RAM like any PC can without the worry of refocusing the app.only to have it reload your session.
Uhh, PC is no better in retaining active session in a RAM-constrained environment.
They simply unload it to storage.
Ever tried using up all your RAM capacity and Windows tries to load it from HDD? Yes, it happens back then.
Also, some apps cleverly used the lifecycle callback to make sure that even if the app process got terminated by the system, the user can go back to where they were before.
Some games I play like Genshin Impact do that. It still forces me to relogin but, full asset reloading is not needed.
@@kamikakushi_ uhhh, this isn't about "using up" RAM or a "RAM-constrained environment," it's about Android not effectively managing large volumes (e.g. 12GB and above). Devices routinely kill sessions long before using more than 75% of RAM. You have to perform convoluted gymnastics to get a 12GB device to even use more than 8GB.
@@nickthaskater So, where do you get this hard limit of 75% from?
I can't seem to find it.
Also, what's the use case of having to use more than 3-4GB of RAM per application?
@@kamikakushi_ I did not say anything about a hard limit. This is not about "3-4GB per application," either. It's about Android's aggressive tendency to kick applications out of RAM despite having plenty of headroom, without offloading the session to storage.
For example, it's impossible to maintain an active, authenticated Citrix remote desktop session in the browser. If you minimize it momentarily to check another application, the session restarts and you need to reauthenticate and start all over again.
As for a use case for more than 3-4GB per app, photo editing applications like Lightroom and video editing applications like LumaFusion, let alone web browsers, can all push that limit.
@@nickthaskater Ah, after reading the android source documentation, some old forums here and there and piece it together, I finally understand about what you wrote.
Sorry if my reply might imply a snide remarks to your suggestions.
Do you think it would be better if we have access to APIs that could make us developers able to understand what's going on behind the curtain with the kernel swap daemon or the low memory killer so that we could develop an app that could react accordingly?
Kind of like onTrimMemory() but more granular.
Let's gooooo
Awesome
looking forward to e2e ui ❤️
The Future of Android will be more restricted as the iOS while the other side tried to be more open.
Each new version of Android is making dev life more miserable. Why so much complexity. Complex and non intuitive code.
I want an Android 15 t-shirt
Does Android have a future? I don't think so. There are always a lot of changes, which cause headaches for developers. Moreover, there are many restrictions for publishing apps on the Play Store. I've quit Android development, and now I'm happy with web development. Google is driving away Android developers.
AFAIK, web development has a much faster changes (i.e. in toolings, languages, important frameworks). Maybe time has changed but, I still prefer the slower tooling changes in mobile development.
Also, Apple put many restrictions as well in their App Store. Google and Apple both do that for a very valid reason. Security and stability.
Every app will be web app
agree
Google Pixel phones great android experience
Any remote job offers related to Android 15?
Yeah man, because everyone knows RUclips comments are where the best tech jobs are hiding. Try Google or, you know, an actual job site. But hey, maybe your future boss is just waiting here for the perfect comment!
{grazie}
👍👍👍
Android
Straight forward is not informational
Edge-To-Edge is crazy! This will not improve UX, it just complicates development, thank you Google!
some people's takes are just dumb
The changes are not that hard to be made. It's not like you have to rework the implementation of OpenSL ES to Oboe or worse, manual support of AAudio
It's similar to how programmatical UIKit of iOS does as well. Yes, it's what iOS have been doing for years.
Endless reason to hate android develpoment 😅
Nice! Android with AI is the future
All my users are asking for edge to edge multiple times a week
- nobody ever.
Pointless complexity for the point of being pointless.