Android Development

Post has attachment

There's a good summary of what's new in Android 9 Pie if you haven't been following the Dev Preview. You should probably take a look, since it starts rolling out to Pixel phone users today!

The wait is over: Android 9 Pie is here! Read the post here → http://bit.ly/...

plus.google.com

Show all 15 comments

Craig Kennedy: I have been out of the Andriod loop for a spell, life! Is Andriod 9 Pie open sourced? Having been rooted in CyanogenMod for years, I am sure there is developer access to the OS right?

Modifying my response after the fact, I missed Zachary's first message at the top where he side loaded.

Ian Lake: +Craig Kennedy - yes, Android 9 Pie's source code is available right now in AOSP for use in custom ROMs

Craig Kennedy: +Ian Lake Sweet, will go look for it. TY

Add a comment...

Post has attachment

Ian Lake

Android Development

AndroidX development moving to AOSP
Very exciting to see AndroidX, Architecture Components, and even alpha libraries like Navigation all being developed in AOSP.

r/androiddev - AndroidX development moving to AOSP

34 votes and 2 comments so far on Reddit

reddit.com

Add a comment...

Ian Lake

Android Development

Navigation 1.0.0-alpha04 is out now!
- app:type has been renamed to app:argType to prevent conflicts with ConstraintLayout 2.0.0-alpha1 and other libraries
- Error messages in Safe Args are now clickable
- Fixed an issue with deep linking and back button

https://developer.android.com/jetpack/docs/release-notes#july_19_2018

Show all 8 comments

Pedro Varela: +Ian Lake thank you very much what do you suggest to solve this problem meanwhile? I have noticed that Google apps if the use Navigation Architecture, only the main activity seem to have a Navigation Graph, other activities just have simple UI . So having two activities with two independent nav graphs it is not recommend or supported so far. Thanks Ian , as usual great job writing this Navigation Architecture.

Daniele Segato: On the block post you say you want to get Feedback on the Navigation API, where can we provide this feedback?

I'd love to be able to manage, as part of navigation:

- drawer with multiple fragments on same level, ex. a bottom tab bar with drawer that stay on on any of the tabs (currently the drawer became an up navigation when you click any of the bottom tab sections)
- hide / show tabbar or other navigation components while navigation (es. some destination should hide the tabbar)
- more in general components that are not part of a particular destinations but are controlled / change in different destinations (toolbar, search bar etc..)

Ian Lake: +Daniele Segato - feel free to look through the existing issues and file new ones: https://issuetracker.google.com/issues?q=componentid:409828

The first one is WAI (same issue as https://issuetracker.google.com/issues/79671564) and the others can already be done with an OnNavigatedListener (or you should use the new Toolbar.setupWithNavController method and just move that code into each destination).

Add a comment...

Post has shared content

Ian Lake

Android Development

Really excited to see the return of Android Dev Summit!

Originally shared by Android Developers - 9 comments

Android Dev Summit 2018

Learn more here → http://bit.ly/2O5rDps

Save the date! Android Dev Summit is coming to Mountain View, CA on November 7th-8th, 2018 at the Computer History Museum. Join us for 2 days of deep technical sessions from and networking with the Android engineering team. Registration and session details will be shared soon. We'll also be live streaming for those who wish to tune in remotely. Hope you can join us! #androiddevsummit

Android Dev Summit | Android Developers

developer.android.com

Add a comment...

Post has attachment

Ian Lake

Android Development

Navigation 1.0.0-alpha03 is now available!
- NavigationUI helpers for Toolbar and CollapsingToolbarLayout
- More types (including Parcelable!) and nullability for Safe Args (note the breaking changes though)
- Lots of bug fixes

Architecture Components Release Notes | Android Developers

developer.android.com

Add a comment...

Post has attachment

Ian Lake

Android Development

Upcoming AndroidDev AMA
Almost 30 of us (myself included) will be available to answer your questions about Android Dev in our upcoming AMA! Add your questions now

r/androiddev - We’re on the engineering team for Android P. Ask us Anything! (starts July 19)

Add a comment...

Navigation Editor and Android Studio 3.2 Beta 1
The Navigation Editor is still experimental and is therefore disabled by default in +Android Studio 3.2 Beta 1. Re-enable it by going to the IDE 'Settings/Preferences' dialog, selecting 'Experimental' in the left pane, then 'Enable Navigation Editor'.

We're tracking updating the Navigation documentation to specifically call this out in this bug: https://issuetracker.google.com/issues/110564366

Add a comment...

Post has attachment

Ian Lake

Android Development

13w

Navigation 1.0.0-alpha02
Alpha 02 of the Navigation Architecture Component is out now with many bug fixes.

For bugs, feature requests, and documentation issues for Navigation, use https://issuetracker.google.com/issues/new?component=409828

For bugs and feature requests for the Navigation Editor, use https://issuetracker.google.com/issues/new?component=404706

Thanks for all the feedback so far!

Architecture Components Release Notes | Android Developers

developer.android.com

Show all 23 comments

Ian Lake: +Kanivel J - as per the material design guidelines [1], "Swipe gestures do not navigate between bottom navigation views."

[1] - the 'Transitions' section of material.io - Bottom navigation

Kanivel J: +Ian Lake Why already stacked fragments are reloading when i come back with device back button or toolbar back button using navigateup() or popbackstack()

Ian Lake: +Kanivel J - Fragments have their views destroyed when put on the back stack, but the Fragment itself and (more importantly) any ViewModel you're using the store data is kept. Are you seeing something different?

Add a comment...

Post has shared content

Ian Lake

Android Development

13w

"Starting today you can publish your APK updates that are compiled against, or optionally targeting, API 28. Publishing an update to Google Play during the preview lets you push updates to users to test compatibility on existing devices, including devices running Android P Beta 2."

Originally shared by Android Developers - 10 comments

Announcing Android P Beta 2 and final APIs!

Read the blog for more info on new features in Android P → http://bit.ly/2Jz9PUp

Get started here → http://bit.ly/2JxUlQE

Today we're excited to announce the release of Android P Beta 2 with final APIs and the official API 28 SDK! Enroll in Android Beta to get the latest version of Android P today on your Pixel 2, Pixel 2XL, Pixel, or Pixel XL device! Also watch for updates from our partners on their Android P Beta devices in the weeks ahead.

Android Developers Blog: Android P Beta 2 and final APIs!

android-developers.googleblog.com

Show all 6 comments

Tihomir RAdeff: But I think there is no appcompat-v7 28.0.0 final version - only alpha. I don't think it is very smart to use alpha library in production.

Ian Lake: +Tihomir RAdeff - FWIW, that's the same code that Google apps ship to production with. Obviously YMMV, test thoroughly, etc., but you wouldn't be the first app to ship with it.

Pradeepa Ravichandran: Am having 32 bit Linux machine am not suppose to update after API 23 .why?

Add a comment...

Post has shared content

Ian Lake

Android Development

16w

From some of the reasons behind why we built the Navigation Architecture Component to the importance of good tool integration to what is still left to do, there's a lot covered in the podcast.

Originally shared by Chet Haase

ADB 92: Navigation Conversation
In which +Tor Norbye and I chat with +Ian Lake and Joe Baker-Malone about the new Navigation architecture component and tool.

http://androidbackstage.blogspot.com/2018/05/episode-92-navigation-controller.html

Episode 92: Navigation Controller

androidbackstage.blogspot.com

Show all 5 comments

Christopher Rucinski: +Ian Lake I am asking this in the same manner from which navigation was also a core part of the framework itself, yet there were better ways of handling it (i.e. Navigation Controller).

It isn't just Accessibility. This would deal with "Tab" Navigation on ChromeOS for Android Apps along with IME Actions integrations with your codebase and Focus Navigation in Accessibility.

These all deal with Navigation within a single "screen" (i.e. Fragment, View, etc...), yet our codebases fall into one of two options. These navigation areas are completely ignored and not implemented, or they are littered throughout our codebase.

Issues
If you implement accessibility in your code, then your XML layout files will be scattered with "focusing" attributes. If you implement ChromeOS support, then you will have additional focusing attributes that you will need to specify. Or you can litter your code with these.

Second, you can group UI elements in Layout Containers (i.e. LinearLayout, etc...) and specify a focusable attribute so TTS will read everything (hopefully correctly, but most likely won't with CoordinatorLayout). You can correct misreadings by using additional Layout containers to get the speech correct (breaking the flatness and speed of CoordinatorLayout just to implement accessibility). A secondary method would be to do this all in code (inflating your codebase, breaking single responsibility, etc...)

Third, everything I said above with TTS will only read text exactly as specified. If you want TTS to be more natural and less "robotic", you can only solve this by inflating your codebase and programmatically updating the views to read how you want the views to read. This is all up to each individual programmer, but I assume there are tested and proven ways to display grouped content to users better.

Fourth, if you plan on providing grouped TTS content while also allowing Focus Navigation, then you will run into issues as listed at this Google CodeLabs Issue Tracker (https://github.com/googlecodelabs/android-accessibility/issues/4). This link shows that there are some ways to mitigate the issue when you are on higher Android API levels, but it isn't fail-safe.

A point I didn't mention above but is also related to navigation (with the keyboard) is soft IME Action support (https://developer.android.com/training/keyboard-input/style#Action).

Wrap-up
As you can see, this issue is also complex, even though accessibility is a core part of the framework itself and has been since the beginning.

Ian Lake: +Christopher Rucinski - I know revamping the Accessibility docs with the current best practices is something actively being worked on as a lot has certainly changed (even in the last year).

Christopher Rucinski: +Ian Lake Sure revamping the docs can help (just like it did for Navigation until it became too much for developers) but by providing a tool built-in to Android Studio (similar to Navigation Controller) you will allow people that never wanted to invest their time into these other forms of Navigation (and supporting features listed above) to actually want to invest some time, while making implementing them much easier for smaller teams and individuals.

That is something that revamping the docs can't really accomplish especially since this area updates a lot over a year. A built-in tool would allow a concise location for developers to find about and implement up-to-date, best-practices for focusable navigation and Accessibility.

Add a comment...

Wait while more posts are being loaded

Press question mark to see available shortcut keys