Google and Apple are continuing to force new deadlines and new obligations on apps publishers and, consequently, us developers.
MOBILE DEADLINES FROM GOOGLE
Starting in August 2018 all new Android apps submitted to Google Play store will need to target Android Oreo.
In November 2018 updates to existing apps will need to do the same. If you have apps in the Google Play store, they will have to be upgraded before November 2018.
In August 2019 all apps will be required to provide a 64-bit version even if they target any native Android libraries. This is not a concern of yours right now.
MOBILE DEADLINES FROM APPLE
They usually announce new versions of iOS around September. Current version is 11 and the lowest supported version is 8. Nobody will be surprised if starting September the lowest supported version goes up on notch, to 9. This means that your apps will be tanked and not shown in the App Store — the old users would have it still on their iPhones but there would be no new downloads.
The obvious way to stay in the App Store is to upgrade your app to iOS version 11. Just recompiling the existing apps and putting “11” instead of “8” as a version of iOS into it may not work.
Having worked for several iOS apps publishers that had to upgrade their software or quit the apps business, I have all the software upgraded and can produce an upgraded app. That would still be at a fraction of cost needed for building a similar app from scratch.
GDPR STARTS ON 25TH OF MAY 2018 — THIS VERY MONTH
It will affect you even you are only collecting email addresses on voluntary basis.
HOW GDPR WILL AFFECT YOU AS A SITE OR APPS PUBLISHER
You would need the sites and apps to adjust the accompanying legal documents at the very least. That’s the change needed on the outside. On the inside, there will be major changes in processing the user data. The main requirement of GDPR is to let the users see what data do you have about them and then you should be able to ERASE that data if the user chooses so. That is a new programming task for both the sites and the apps and will require implementing additional procedures and back end techniques.
For instance, if you collected email, nickname and the real name of the user when entering the site or the app, these data would be stored in a database on your Internet server. You have to let the user see the data you have on them — usually using one or two clicks at the most. That is a new programming requirement for the app. If the user orders you to erase their data from the system, you should also have that capability built into the software as well.
Probably, you will want someone from your personnel to oversee that kind of permanent change in the data.
I can fill in the parts of you apps and / or sites so that they would be GDPR compliant. Send me an email at firstname.lastname@example.org.
All this is a new kind of headache not only for apps publishers but for the corresponding developers as well.
Kind regards, Dusko
00 381 64 1385043