Profile

Cover photo
Peter Friese
Works at Google UK Limited
Attended Nordakademie
Lives in London, United Kingdom
965 followers|389,447 views
AboutPostsPhotosYouTubeReviews

Stream

Peter Friese

Shared publicly  - 
 
 
New and improved Google Play services for your Android apps: xmn.io/1Rt9RaB
The latest Google Play services 8.1 for Android release brings some exciting new APIs, such as Barcode and Face detection, as well as simplified management of your sessions. This release also comes with some improvements to the Xamarin developer experience that we have brought to Google Play services for Android components and NuGets. Add What You Need …
View original post
1
Add a comment...

Peter Friese

Shared publicly  - 
 
If you're using the NDK to build Android Wear applications, you should read this to make sure your apps will run on Intel-based wearables.

Are there any Intel-based Android Wear devices, I hear you ask? Well - there have been a number of announcements for a number of pretty exciting devices, so you should definitely care :-)
 
There have been a number of press-releases about upcoming Android Wear devices containing Intel x86 processors. Some developers have been building applications for Android Wear using the NDK, and providing only armeabi-v7a shared libraries in their wearable APK. With the impending arrival of these new Intel x86 wearables, APKs built for only ARM will fail on these new devices.

Note: if you are only working with Java code, there is nothing to do here, since your APKs are in portable bytecode, and will work on any architecture. You only need to read this if you are using the NDK.

So what do you need to do to add support for x86? It is very easy. You simply need to edit your build.gradle for the wearable module to include both armeabi-v7a and x86 in your abiFilters, and then recompile. Gradle will then build a combined wearable APK, which contains binaries for both architectures. The wearable APK is then embedded into the regular phone APK, as usual.

I have an open source project where you can see how the build process works. The wear/build.gradle file contains the following now:

ndk {
  moduleName "native-jni"
  ldLibs "log"
  stl "stlport_static"
  abiFilters = ['armeabi-v7a','x86']
}

You can see the build.gradle file, and the rest of the GitHub project, here:
https://github.com/waynepiekarski/android-glider/blob/x86/wear/build.gradle#L13-L18

How can you determine if your final APK is built correctly? Firstly, you should unzip the phone APK. Then, unzip the embedded wearable APK located in res/raw. There should be two binary .so files, where "native-jni" will be replaced with whatever you used in moduleName in your build.gradle:
  lib/armeabi-v7a/libnative-jni.so
  lib/x86/libnative-jni.so

If you find yourself in a situation where your wearable APK will still not install, you should check adb logcat on the wearable device. If there are problems caused by not having the right ABI binaries present, you will get the error INSTALL_FAILED_NO_MATCHING_ABIS represented as code -113 in the logcat output:
  W/NativeHelper(  457): Failure copying native libraries [errorCode=-113]
  E/WearablePkgInstaller( 1568): Package install failed null, returnCode -113

If you have any more questions about this, please discuss it on this post.
View original post
1
Add a comment...

Peter Friese

Shared publicly  - 
 
 
In case you haven't seen it already, we have developed a Udacity class on developing apps for Android Wear. Previously it was part of our Ubiquitous Computing class, but we provide it separate now for those developers who want to only learn about Android Wear.

So you can join me as I teach you how to get started with Android Wear! Its a great way to be walked through all the important steps to develop apps, and how to use the existing samples to see how things should be done.

http://android-developers.blogspot.com/2015/10/new-courses-developing-watch-apps-for.html
View original post
1
Add a comment...

Peter Friese

Shared publicly  - 
 
 
Did you know that London has its own chocolate museum? When better to visit it than #ChocolateWeek?
View original post
1
Add a comment...

Peter Friese

Shared publicly  - 
 
 
How does Xtend compare to +Java 8?

This question pops up from time to time. Most people forget that Xtend has many more features than just lambdas. But even if we just look at lambdas, the conciseness and clean syntax of #Xtend  is obvious.

Here are two screenshot from our freshly made +IntelliJ IDEA plugin.

The first picture shows both languages using the very same API (Java8 stream API that is). The second shows a comparison using the language's idiomatic style.

You can see that the Xtend version is much shorter and at the same time doesn't lack any important information. It just leaves out ceremony and focusses on the necessary. That's how it should be.

The Numbers:
 - Java : 205 characters
 - Xtend Stream API : 164 characters
 - Xtend idiomatic : 105 characters
View original post
1
Add a comment...

Peter Friese

Shared publicly  - 
 
Specifies that an app wants a particular permission, but only if the app is running on a device with SDK version 23 or higher. If the device is running SDK version 22 or lower, the app does not have the specified permission. This element is useful when you update an app to include a new feature that requires an additional permission. If a user updates an app on a device that is running SDK version 22 or lower, the system prompts the user at inst...
View original post
1
Add a comment...
Have him in circles
965 people
Sheila C. Kile's profile photo
Matthias Treitler's profile photo
Matthias Erche's profile photo
Dinh Tuyen's profile photo
Koun khmerLDP's profile photo
Sarah Nelson's profile photo
Sudipta Deb's profile photo
Thomas Darimont's profile photo
Henning Dodenhof's profile photo

Peter Friese

Shared publicly  - 
 
This is really useful, especially for business mails.
 
Smart Reply - a deep neural network that writes email

Replying to an emails on a mobile device can be a challenge, even for short replies. What if there were a system that could automatically determine if an email was answerable with a short reply, and compose a few suitable responses that you could edit or send with just a tap? 

Smart Reply, which will be launching later this week, is built on a pair of recurrent neural networks, one used to encode the incoming email and capture the gist of what is being said and the other to predict and compose grammatically correct possible responses. 

Head over to the Google Research blog to learn more.
26 comments on original post
1
Chris Ainsley's profile photoPeter Friese's profile photo
2 comments
 
It doesn't automatically send, instead the canned response is inserted in your reply and you can edit as needed.
Add a comment...

Peter Friese

Shared publicly  - 
 
 
New in Android Samples: Authenticating to remote servers using the Fingerprint API

Nobody likes typing in passwords, especially on mobile phones. But we’ve got the cure for the password blues in this week’s Android samples release.

Join us as we take a deep dive into Android 6.0’s new support for fingerprint sensors (like Nexus Imprint). We’ll show you how the Fingerprint API interacts with the system’s hardware keystore and how you can add secure fingerprint authentication to your app’s client- or server-side code.

#Marshmallow

http://goo.gl/vGVIVX
5 comments on original post
2
Add a comment...

Peter Friese

Shared publicly  - 
 
 
Xamarin Developer Evangelist James Montemagno shows you how to easily authenticate users with Android’s Confirm Credential: xmn.io/1Xfxhnt
There are a number of ways to authenticate users on mobile devices, from traditional passwords and pins to new biometric fingerprint sensors. Most users are already using one of the most secure mobile authentication implementations, the device lock screen. With Android Marshmallow and the new Confirm Credential API, it’s now possible to utilize the lock …
View original post
1
Add a comment...

Peter Friese

Shared publicly  - 
 
 
Getting your app content found on Google just got easier. App Indexing is now compatible with HTTP deep link standards for iOS 9, as it has been on Android from the beginning. That means that you can start getting your app content into the Search results page on Safari in iOS, simply by adding Universal Links to your iOS app, then integrating with our SDK. With this improvement, we will no longer support new integrations on iOS 7 and iOS 8. Users will start seeing your app content in Safari on iOS at the end of October.

And, of course, on Android, you can still get your content into the Search results page, autocompletions, and Now on Tap by adding HTTP deep links and integrating with the App Indexing API.

To learn about getting your app content found on Google Search, visit g.co/AppIndexing. And to learn more about leveraging Search to increase engagement with your content, both in apps and on the web, visit g.co/DeveloperSearch.
9 comments on original post
1
Add a comment...

Peter Friese

Shared publicly  - 
 
 
Update your Android apps to #AndroidMarshmallow with today's latest update to Xamarin.Android: xmn.io/1WQ4zcz
Android Marshmallow is here! Update your Xamarin.Android apps with the latest features of the new release today.
View original post
1
Add a comment...
People
Have him in circles
965 people
Sheila C. Kile's profile photo
Matthias Treitler's profile photo
Matthias Erche's profile photo
Dinh Tuyen's profile photo
Koun khmerLDP's profile photo
Sarah Nelson's profile photo
Sudipta Deb's profile photo
Thomas Darimont's profile photo
Henning Dodenhof's profile photo
Work
Occupation
Developer Advocate
Employment
  • Google UK Limited
    Developer Advocate, 2014 - present
  • Zühlke Engineering
    Software Architect / Software Engineering Consultant, 2011 - 2014
  • itemis
    Head of Mobile Development, 2008 - 2011
  • Gentleware
    Software Architect, 2007 - 2008
  • Lufthansa Systems
    Software Architect, 2000 - 2006
  • Lufthansa
    Software Engineer, 1996 - 2000
Places
Map of the places this user has livedMap of the places this user has livedMap of the places this user has lived
Currently
London, United Kingdom
Previously
Norderstedt, Germany - Hamburg, Germany - Toronto, Canada - Frankfurt, Germany
Story
Tagline
Making mobile more social, one app at a time.
Introduction
Peter works as a Developer Advocate at Google in the Developer Relations Team in London, UK. He is a regular open source contributor, blogger, and public speaker. He is on Twitter at @peterfriese and on Google+ at +PeterFriese. His blog can be found at http://www.peterfriese.de
Bragging rights
Has been told his bass groove has an African touch.
Education
  • Nordakademie
    Comp. Sci., 1996 - 2000
Basic Information
Gender
Male
Tolles Schwimmbad mit vielen Attraktionen (mehrere Rutschen, Wellenbecken, Solebecken, 50m Aussenbecken, 1m und 3m Sprungbecken innen, Kinderbereich, Spassbereich, etc.). Auch das leibliche Wohl kommt nicht zu kurz. Eintrittspreise sind vergleichsweise moderat.
Public - 3 weeks ago
reviewed 3 weeks ago
Einer der schönsten Parks in Hamburg. Große Rasenflächen laden zum Picknick oder Ballspielen ein. Alternativ: Spaziergang durch den Park mit anschliessender Rast bei Ralph's Café in der nordwestlichen Ecke des Parks.
Public - 3 weeks ago
reviewed 3 weeks ago
Herrliche Aussicht (und ein beliebter Platz für Pokémon GO!)
Public - 3 weeks ago
reviewed 3 weeks ago
Kompetente Beratung, freundlicher und zügiger Service. Das Sortiment ist eher auf sportliche und höherwertige Fahrräder angelegt, wer also ein Hollandrad sucht, wird im Ladensortiment eher nicht fündig werden. Allen anderen wird das Herz höher schlagen :-)
Public - 3 weeks ago
reviewed 3 weeks ago
9 reviews
Map
Map
Map
Solide Blockhouse-Qualität, netter und unaufdringlicher Service.
Public - 3 weeks ago
reviewed 3 weeks ago
Gute Auswahl an Speisen, recht großzügige Portionen. Mein persönlicher Favorit: der Mangosalat!
Public - 3 weeks ago
reviewed 3 weeks ago
Great view of the bay from the café on level 6!
Public - a year ago
reviewed a year ago