This article was first published on Official TenX Blog - Medium
In 2018, the TenX product and engineering teams decided to migrate their existing native mobile apps to React Native. You can read the full motivation behind this decision in the earlier posts from our Product team here and here.
Starting in the summer, the engineering team began rebuilding the mobile apps from scratch using React Native. We were a small team driven by a pressing business need to ship a replacement for our native apps before the upcoming relaunch of the TenX Card.
By early December, we had shipped a new version of the TenX Wallet to our users on iOS and Android, fully rewritten in React Native.
Now, in 2019, the new TenX Wallet has supported the official relaunch of our cards in Singapore and is fully ready to support our card rollout throughout Asia and Europe.
In this post, I’ll discuss the migration to React Native from the engineering side.
One of the key decisions we made from the start is to transition our APIs to use GraphQL. However, at the time our native apps were communicating with our backend using a traditional REST API, so this meant we had to build a GraphQL server in parallel as we developed the React Native app. This would require additional work, but there were two key factors which made this tradeoff worthwhile:
- GraphQL would allow us to move very quickly on the frontend by giving us a flexible, typed API which we can manage with a client like Apollo.
- Our backend system was simultaneously ...
To keep reading, please go to the original article at:
Official TenX Blog - Medium