There’s a useful new article by COBE on how they use Google sheets and the same keys to provide for localisations across iOS and Android. While the article is useful, here are some comments from past experience:
- When using common keys, remember there will always be some error cases, and hence messages, on iOS and Android that aren’t on the other platform.
- Localisation of strings without knowing their context can lead to misunderstandings. Review all changes in the UI, preferably by someone who is fluent in the target language.
- Localisation sometimes hits problems with fitting strings to tight UI locations when strings are longer than expected. This tends to be where texts have been justified centre or right to fit.
- Think about graphics that might also include text.
- On giving clients or product owners the power to change the strings files, this relies on them correctly matching strings to locations in the app. Also, incorrectly specified special characters and hence characters codes in the strings will break builds.
Sensor Tower are reporting U.S. iPhone Users Spent An Average of $40 on Apps in 2016. This is an increase of $5 compared to the previous year. Games represent more than 80% of the revenue:
These numbers show that, unless you are developing games, an app store revenue-driven business model isn’t likely to be viable.
I have always found app T&Cs to be one of the most contentious parts of an app and one of the things that change most often prior to publishing. Someone tends to draft something and it subsequently gets changed in many subtle ways as it does the rounds in the company.
So how do you get your first draft? What if you are a ‘one man band’ and need something simple and suitable? Ali Muzaffar has a great blog post on the topic. There’s also a free policy generator by Nishant Srivastava based on Ali’s template.
There’s a thought-provoking post by Carolin Milanesi of Creative Strategies on The Smartphone: Our Most Valued Possession When it Comes to Privacy and Security. Their study showed that security on smartphones matters most to consumers. However, security matters differently depending on the kind of service. For example, people expect tighter security for email clients than for social media apps.
While all this might seem obvious after inspection, it has implications for apps. Apps and hence developers need to apply a level of privacy and security appropriate to the app’s use. What you, as a developer, might think as an acceptable level of security might be different to consumers’ expectations or even the requirements of your business. These things can be important and demand extra consideration.
Gartner has new press release on smartphone sales. While Gartner concentrates on the battle between Apple and Samsung, the more interesting part for mobile developers is at the bottom of the press release where Android has extended its lead over iOS by 3.2%:
Android now has 81.7 market share. However, Google isn’t standing still and seems to be experimenting with replacing the kernel under Android and Chrome.
Being at the receiving end of enquiries for iOS and Android development has made me realise how many people and companies don’t really know what they are getting into. Some haven’t a clue, not even a hunch, how much effort is involved. Most see a set of screens as something simple. They don’t realise the complexity of what goes on underneath and the consequent communication with other systems and platforms. They don’t realise there are ‘quick and dirty’ ways of doing things and slower and more future proof ways of implementing things, both of which are valid depending on the business context. They don’t think about edge error scenarios, user experience, measuring through analytics and other things like localisation and even the complexities of time. In some cases, there’s no thought as to whether the project is technically feasible.
Ordinarily, this isn’t a problem because many of these things are taken care of by the developer. However, these types of people/companies also tend to not know how to choose a developer. All they think about is cost or daily rates. which gravitates them to developers who don’t know or don’t take care in what they are doing. Not knowing what factors are important and wanting implementation at the lowest cost is obviously a recipe for a failed project.
Google is Integrating Progressive Web Apps more deeply into Android. This will make web apps 1st class Android citizens in that they will be able to be shown in the app drawer and receive incoming intents.
If you are a long time reader of this site, you will know I am not a great fan of hybrid web apps masquerading as ‘native’ apps. They are usually less secure, have significantly less technical capability, have UI performance problems and don’t tend to use the Android OS look and feel. Allowing web apps into the app drawer is a backward step in my opinion.
There’s a new post on the Android developer blog on Engaging users during major events: How The Guardian used innovative notifications. The Guardian newspaper used the new notifications functionality in Android 7.0 Nougat to create a continuously updating notification which was persistent on their lock screen:
“Promoting live updates (via the notification) resulted in 103% increase in daily installs during election week. “
I am currently involved in apps using iBeacon and Eddystone Bluetooth beacons. It occurred to me that an interesting partner for persistent notifications is use with beacons. Detection of beacons could drive changes in a notification based on a user’s indoor location. This might be used in visitors spaces such as galleries and museums. It might even be used to direct users along an indoor route.
Learn more about notifications in Android Nougat
Learn more about beacons