Profile cover photo
Profile photo
Ash Davies
239 followers -
Android software craftsman in Berlin, policy advocate and public speaker
Android software craftsman in Berlin, policy advocate and public speaker

239 followers
About
Ash's posts

Post has shared content

Announcing updates to Google’s Internet of Things platform: Android Things and Weave

Today we are announcing a full range of solutions to make it easier to build secure smart devices and get them connected. We are releasing a Developer Preview of Android Things, an operating system for connected devices that has the support and scale of existing Android developer infrastructure. You can now develop IoT software using Android Studio and the Android SDK. We are also updating the Weave platform to provide an easy way to add cloud connectivity and management to devices, and enable access to Google services like the Google Assistant and many more over time.

Learn more about Google’s IoT platform from our blog post at https://goo.gl/eENGtu, and join our new Google+ community at https://g.co/iotdev.
Photo

Post has shared content

Post has attachment
Google stylized my trip to Hamburg earlier this year

Post has shared content
New Android Wear Developer Preview 3

Today we are launching the Google Play Store on Android Wear in the third developer preview for Android Wear 2.0. In addition, we are releasing a number of enhancements including updates to the Complications API, launching the new WearableRecyclerView to better take advantage of circular displays when displaying vertical lists, inline actions for notifications, Smart Reply as well as fixes for a number of bugs you helped us identify (theatre mode anyone?). Let us know what you think and please send us your feedbacks!

Read more here: goo.gl/l27GJz

#AndroidWear
Animated Photo

Post has attachment

Post has attachment
Google Allo finally released!

Post has shared content
Google Duo is out, Deus Ex GO, the future of Hangouts - Android Apps Weekly -

Hey all,
Having many read articles and implemented myself various different application structures for use with Dagger I'm curious about the preferred implementation. In particular regarding sub-scoping components for different features, and component persistence.

Do most people prefer to go for the application/activity scopes or for feature based? and where to store the component if not using the application/activity style?


Post has shared content
Tip: Try slowing down the animations on your phone!

I'm working on some animations and accidentally left my phone on "animator duration scale" 5x over the weekend. I was about to turn it off but decided to keep it on as an exercise in zen and to observe movement. I always perceived that my phone moved, but I've been surprised how detailed many system animations are! My favorites so far are the lock screen in pattern mode, everything in the Search app, and this Hangouts FAB animation.

* You can see a drawing artifact if you look closely -- not sure if it is just on N!
Animated Photo

Post has attachment
This is only rumour, but the idea has started gaining some traction, I'm not really sure what Google would want to obtain by doing this. The Nexus line is already a very strong brand and the hardware manufacturers generally build very reliable handsets.
Wait while more posts are being loaded