In 2015, few apps had force upgrading mechanisms in place. Nearing 2021, most mature apps have put this approach in place, recognizing the need to force retire old versions of the app. Old app versions might stop working when a backend API is retired, and they might be expensive to test, support and keep backwards compatible. The catch with force upgrade is you need to build it much earlier than when you plan to use it. ...
There’s a high likelihood that your app and your development process needs to adhere to certain compliance and privacy guidelines. PII - Personally Identifiable Information - should not be accessible to anyone but people who should access these details. No mobile engineer, customer support folks, or people working at the company should be able to access this information. GDPR (General Data Protection Regulation) - an official EU regulation - has further expanded the scope of PII. ...
The shorter the feedback cycle between detecting issues with your code, the more productive both engineers and teams will be. While getting feedback on your code at code review is great - would it not be even better to get instant feedback, even before you submit your code to code review? Productive teams put advanced code checking infrastructure in place early on: exactly to help with rapid feedback on “easy to spot” code quality issues. ...
Mobile app performance is something you rarely need to worry about with small apps - and something that becomes increasingly important, as your app - and mobile team working on the app - grows. Users will eventually abandon problematic apps, according to a 2015 Techbeacon study. Since the study, expectations for “snappy” apps have likely only increased. perf.dev is an industry-leading mobile performance platform from the creators of Nanoscope. The platform enables a proactive workflow for managing mobile performance. ...