3 things to remember while migrating an Android app

Migrating an app, especially one implemented by someone who should probably do other things for a living, isn’t always an easy business. Nothing overly challenging, nothing technically impossible, but there are still things one should be aware of from the start to avoid excessive hassle, spare the client some of the costs and keep a good reputation. We’ve recently excelled across the board while implementing a project for a Scandinavian client and we’d like to share some of the insights we’ve gained with you. Perhaps, you’ll find something useful for your future migration endeavors.

migrating

Our client, a Swedish innovation agency that caters to several household names that you’ve, normally, been aware of since you were a kid, approached us to improve the performance of one of their mobile apps. The app is intended to conduct advanced employee surveys on the fly. It is part of a larger system that also included a Web-based application.

See More:- Windows Hosting Vs. Linux Hosting

1. Large Amount of Code to Migrate: Use React Programming

There were loads of code to deal with. We knew at once this amount of code would overload the system very significantly and slow down the migration process quite a bit. In addition, the number of modifications that would have had to be made across this data would have been very large. In order to avoid this, we decided to bring RX Android into play.

As the technology allows using threads to create queries that retrieve only the data that is required at the moment, we’ve managed to avoid both of the above issues. The code migration process has been smooth and relatively expeditious.

2. Increasing the App’s Responsiveness: Use Custom Android

The client’s app didn’t sport a GUI you could refer to as extremely user-friendly or optimal from the point of view of UX. Moreover, the app was not responsive enough and we were faced with the need to enhance it’s responsiveness very considerably.

While dealing with the latter task, we noticed that the external library utilized by the app, accounted for some 50% of the app’s size.

See More:- 7 Ways To Free Up HD Space On Windows

3. Use Unit Testing While Migrating: Longer, But Highly Efficient

Moving an app to a new version is bound to make a bunch of bugs surface. Willy-nilly, you’ll have to deal with them in midstream. More so, we had to maintain both versions of the app and ensure compatibility between them. This increased the odds of us making a critical mistake, either in the old version or in the new one, that would then prove to be extremely hard to correct.

We decided that it would be prudent to spend more time on QA than hunt for well-hidden bugs later. We divided the app’s architecture into modules, composed a set of tests and used Mockito to test the app in a modular fashion.