Now that we’ve shown you a few of the features available in MyDriveTime for Students we’re going to talk you through our build process.
Building MyDriveTime for Students
The build process involved deciding on whether to use Ionic3 or Ionic4 framework for building the app. We carried out multiple tests on Ionic4, which was launched recently, to make sure that it was stable and met the technical requirements of the app. Once we established that the framework was stable and met the apps needs, we decided to go with Ionic4 over 3 for a number of reasons.
The major reason was access to the latest features such as web components and CSS4 variables. Most of the major plugins were now being built for Ionic4, which meant less work maintaining plugins on top of benefits like performance improvements and quicker bug fixes. We did decide to stick to Ionic Angular instead of risking Ionic Vue even though at Hinge our framework of choice if typically Vue. Ionic Vue had not yet been released for production and due to our tight deadline, it would be too much risk to use this.
After deciding on Ionic4, we looked into the overall architecture of the app. This was made fairly straightforward using a highly opinionated framework like Angular. The basic architecture involved subscribing to HTTP Services to get the necessary data from the API, converting Observables to Promises and then populating the app with data or displaying the appropriate empty states. The app uses Cordova plugins for accessing native features like sending SMS notifications and checking network connection.
The app was built in an iterative fashion with continuous input from the different stakeholders who were given access to early alpha and beta versions. Their feedback was incorporated based on the priority and urgency along with fixing the bugs they might have found during the testing.
Technologies we’ve used