Being first to the market with both an iOS and an Android app was a matter of survival. When we were about to release our very first version of the FAIRTIQ app, we had good reasons to think that competitors were working on very similar apps. If you are not familiar with the FAIRTIQ product, I suggest you first read the blog post: The Journey of a Journey that describes in detail how the FAIRIQ app and post-price ticketing work. Finally, I’ll give an overview of the current state and I’ll list some lessons learned during this project. I’ll highlight some of the unexpected issues we had to deal with along the way and the changes of direction that the project took. In this blog post, I tell the story of the transition from the first cross-platform app implemented with Xamarin to a fully native FAIRTIQ app. As such, I accepted this new challenge with enthusiasm. Even though I wasn’t an expert in mobile development, I had some basic knowledge in both iOS and Android gained during other projects as a consultant. I had a good understanding of the FAIRTIQ system since I worked as a backend developer consultant and Scrum master during the implementation of the first version in 2016. The goal was to extract the tracking logic from the existing app and to put it into a Software Development Kit (SDK) making it usable by other apps.īy that time, I was working for a consulting company. Roughly four years ago, in April 2017, the CTO of FAIRTIQ asked me to take the lead on the modularisation of the FAIRTIQ app. FAIRTIQ-App Reloaded From a monolithic cross-platform to a modular native app
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |