Android Developers
918,369 followers -
A place for Android developers everywhere to meet, share and discuss the latest on Android development
A place for Android developers everywhere to meet, share and discuss the latest on Android development
918,369 followers
Android Developers's interests
Android Developers's posts
Post has attachment
Public
Android N Developer Preview 2, out today!
The 2nd Developer Preview of #AndroidN is out today, bringing Vulkan, support for Emojii Unicode 9, launcher shortcuts and more!
http://goo.gl/OYIZtb
The 2nd Developer Preview of #AndroidN is out today, bringing Vulkan, support for Emojii Unicode 9, launcher shortcuts and more!
http://goo.gl/OYIZtb
Post has attachment
Public
One day left to enter the Android Experiments I/O Challenge. Submit your experiment to win a trip to Google I/O 2016: https://goo.gl/oQLmyg
Post has attachment
Public
Android Support Library 23.3 available now
This release of the Android Support Library fixes a number of bugs in Support v4, AppCompat, RecyclerView, MediaRouter, Design, and Preferences. See the revisions page (http://goo.gl/gnS6b2) for a full list of closed issues.
If you’re using Support v4 Fragments, nested fragments will now receive callbacks to onRequestPermissionsResult() (in addition to callbacks to onActivityResult(), fixed in 23.2.1).
For AppCompat users, we’ve decided to remove the functionality which let you use vector drawables from resources on pre-Lollipop devices due to issues found in the implementation in version 23.2.0/23.2.1 [https://goo.gl/u5suZB, https://goo.gl/fW5Tyd]. Using app:srcCompat and setImageResource() continues to work.
One new API that is now available in Support v4 is AppLaunchChecker which your app can use to determine if the user has specifically launched your app from their launcher/home screen (compared to only interacting with it via implicit intents or other interactions).
Please continue to file any Support Library bugs at https://goo.gl/Xj4A9f
This release of the Android Support Library fixes a number of bugs in Support v4, AppCompat, RecyclerView, MediaRouter, Design, and Preferences. See the revisions page (http://goo.gl/gnS6b2) for a full list of closed issues.
If you’re using Support v4 Fragments, nested fragments will now receive callbacks to onRequestPermissionsResult() (in addition to callbacks to onActivityResult(), fixed in 23.2.1).
For AppCompat users, we’ve decided to remove the functionality which let you use vector drawables from resources on pre-Lollipop devices due to issues found in the implementation in version 23.2.0/23.2.1 [https://goo.gl/u5suZB, https://goo.gl/fW5Tyd]. Using app:srcCompat and setImageResource() continues to work.
One new API that is now available in Support v4 is AppLaunchChecker which your app can use to determine if the user has specifically launched your app from their launcher/home screen (compared to only interacting with it via implicit intents or other interactions).
Please continue to file any Support Library bugs at https://goo.gl/Xj4A9f
Post has attachment
Public
Join us in a celebration of creativity and code - and enter to win a trip to Google I/O 2016. Enter your Android Experiments today: https://goo.gl/8nnGXR
#io16
#io16
Post has attachment
Public
Android Developer Story: Video editing app WeVideo increases user engagement by 100% with material design
Video editing platform WeVideo, first launched their app on Android. Watch President & CTO, Krishna Menon, and Head of Mobile Development, Oleg Tsaregorodtsev, at WeVideo, explain how relaunching their app with material design and using other Google Play features increased user engagement by 100%.
https://goo.gl/rb7eJz
Video editing platform WeVideo, first launched their app on Android. Watch President & CTO, Krishna Menon, and Head of Mobile Development, Oleg Tsaregorodtsev, at WeVideo, explain how relaunching their app with material design and using other Google Play features increased user engagement by 100%.
https://goo.gl/rb7eJz
Post has attachment
Public
Let’s say you’ve got some 20 bitmaps being decoded on a worker thread. Well, what happens if your activity is destroyed before that work completes?
In this video Doug Stevenson explains Loaders. A super-helpful class that can give you insight into how the activity lifecycle is changing, so that you can better understand how to address threaded work that might be in flight.
https://goo.gl/xVJUe1
#Perfmatters
In this video Doug Stevenson explains Loaders. A super-helpful class that can give you insight into how the activity lifecycle is changing, so that you can better understand how to address threaded work that might be in flight.
https://goo.gl/xVJUe1
#Perfmatters
Post has shared content
Public
Follow the new +Android Studio page to learn about each new release of Android Studio, get pro-tips, and all the Android Studio announcements the moment they make them.
We’re really excited to hear your experiences with Android Studio 2.0 - we created this page so you could tell us directly what you think!
Post has shared content
Public
Android Studio 2.0 has been promoted to a stable release!
Android Studio 2.0 is focused on build performance, with brand new features like Instant Run and the new & dramatically faster emulator.
Update your version of Android Studio now, to take advantage of all the new features.
Not using Android Studio? There’s never been a better time to start.
We’ve been testing this release in Canary and Beta for months, so we’re excited that it’s now ready for use by all Android developers.
YouTube: https://www.youtube.com/watch?v=xxx3Fn7EowU
Blog:
http://android-developers.blogspot.com/2016/04/android-studio-2-0.html
Android Studio 2.0 is focused on build performance, with brand new features like Instant Run and the new & dramatically faster emulator.
Update your version of Android Studio now, to take advantage of all the new features.
Not using Android Studio? There’s never been a better time to start.
We’ve been testing this release in Canary and Beta for months, so we’re excited that it’s now ready for use by all Android developers.
YouTube: https://www.youtube.com/watch?v=xxx3Fn7EowU
Blog:
http://android-developers.blogspot.com/2016/04/android-studio-2-0.html
Post has shared content
Public
‹
›
Google I/O #TB: How it all started in 2007
4 Photos - View album
Google I/O #TB: How it all started in 2007 (Post 1/10)
When: May 31, 2007
Where: Beijing, Hamburg, London, Madrid, Moscow, Mountain View, Paris, São Paulo, Sydney, Tokyo
Highlights: Gears, Geo, Mapplets, Web toolkit, YouTube API
Today isn’t Thursday. But we’re still in a #TB mood, so we’ve decided to take you on a tour through memory lane and recap our favorite moments from past I/Os! Lets start from the very beginning...
Back in 2007, we held the first ever Google Developer Day across 10 countries, aiming to bring the dev community worldwide closer together and improve knowledge sharing. Googlers and attendees had great conversations in a fun environment with games and sweet treats on the side. This multi-location developer event was an evolution of the Geo Developer Day in 2006 and inspired the creation of Google I/O a year later!
Visit the #io16 website for the latest on this year’s event: google.com/io. #TB
When: May 31, 2007
Where: Beijing, Hamburg, London, Madrid, Moscow, Mountain View, Paris, São Paulo, Sydney, Tokyo
Highlights: Gears, Geo, Mapplets, Web toolkit, YouTube API
Today isn’t Thursday. But we’re still in a #TB mood, so we’ve decided to take you on a tour through memory lane and recap our favorite moments from past I/Os! Lets start from the very beginning...
Back in 2007, we held the first ever Google Developer Day across 10 countries, aiming to bring the dev community worldwide closer together and improve knowledge sharing. Googlers and attendees had great conversations in a fun environment with games and sweet treats on the side. This multi-location developer event was an evolution of the Geo Developer Day in 2006 and inspired the creation of Google I/O a year later!
Visit the #io16 website for the latest on this year’s event: google.com/io. #TB
Post has attachment
Public
Pivotal with +Reto Meier is Asynchronous Pair Programming at Scale
You can watch as he makes mistakes (and debugs them), talks through decisions (and goes back on them later), and develops an app architecture (then build something that often ignores it). He’ll get my code reviewed by other engineers, ask for advice, and even look stuff up on Stack Overflow.
Season 1 will demonstrate the best practices for building context-aware Android apps to offer the best user experience, and minimize battery drain by updating an old app to take advantage of the latest location and context features available on Android. By the end of the season, you’ll not only have the best-practice location and context implementation, but you’ll have heard why it should be done that way, and seen how the code evolves along the way.
Read more with this Medium article: https://goo.gl/CUQWkd
Pivotal playlist: https://goo.gl/BGiZnX
Video Teaser: https://goo.gl/vt7DSr
You can watch as he makes mistakes (and debugs them), talks through decisions (and goes back on them later), and develops an app architecture (then build something that often ignores it). He’ll get my code reviewed by other engineers, ask for advice, and even look stuff up on Stack Overflow.
Season 1 will demonstrate the best practices for building context-aware Android apps to offer the best user experience, and minimize battery drain by updating an old app to take advantage of the latest location and context features available on Android. By the end of the season, you’ll not only have the best-practice location and context implementation, but you’ll have heard why it should be done that way, and seen how the code evolves along the way.
Read more with this Medium article: https://goo.gl/CUQWkd
Pivotal playlist: https://goo.gl/BGiZnX
Video Teaser: https://goo.gl/vt7DSr
Wait while more posts are being loaded