“What does having a relevant pool of equipment mean when I have to test applications? If I’d like to create a test set of mobile devices from scratch, where should I begin? My testing pool hasn’t been updated for a long time; what criteria should I check to update it?”
This week, Google held its annual developer conference, Google I/O. While the keynote was massively focused on Android (with announcements for Android L, Android Wear, Android Auto or Android TV), it was still too short for all Android-related news. Luckily, Google provides additional sessions during I/O which yield tons of information.
Geofencing is a technical word for a quite simple concept: it’s all about setting virtual areas and monitoring a smartphone entry and exit of these areas. The main interest is to allow a developer to fire notifications (based on geolocation) even in the background or when the app isn’t running. On iOS, if your app was not active, it can be awakened for a few seconds to handle the geofencing event. The goal of this article is to summarize basic knowledge on the subject, through the eyes of an app maker.
It is getting hard to publish an app where forms are not mandatory. Users are exposed to input data through forms in order to access the service (login, registering), achieve a task (searching, checking out) or complete secondary actions (for instance getting in touch with the editor). Constraints due to the mobile environment (screen sizes and the digital keyboard among many others) make forms a major traffic leak. To the question “What makes you uninstall an app?”, 38% of Android users answer the need to fill a form for registering. Let’s take some time to think about problems users can encounter.