This article was first published on Official TenX Blog - Medium
Embracing React Native for Lean Mobile Development (Part 1 of 2)
A look into how and why we migrated the TenX Wallet apps to React Native
As a preface to this technical piece on our mobile app, I’d first like to introduce Andric Tham, Product Manager and honorary member of Engineering (our product managers push good code too!). Andric was instrumental in putting together a proposal and working with various engineers to evaluate RN as an alternative to our native apps.
— Alvin Jiang, VP Engineering & Product
In 2018, we decided to rewrite our flagship app, TenX Wallet, from standalone native iOS/Android apps to a unified React Native codebase.
Launched two years prior, the Wallet app went through multiple design iterations, and accumulated significant technical debt.
In the second part of this story, we’ll dive into the criteria we used to evaluate this decision, which will hopefully help teams in a similar situation decide the best mobile development approach for them.
? Background and motivation
About one year ago, the Wallet team started to get into quite a tricky spot.
Support tickets were piling up. Our backlog of bugs was growing faster than we could chew through it. With every new feature we built, new bugs emerged.
Each new feature shipped felt like we were moving one step forward and two steps back.
With each release, we were no longer delivering significant value, but found ourselves reacting to issues as they came in. We were fixing them as quickly as we could, but never ...
To keep reading, please go to the original article at:
Official TenX Blog - Medium