In last year’s business case about Keytrade’s future-proof online banking and trading platform, we put forward React Native as the next step in developing the mobile app version. A year ago, icapps ran a PoC to determine whether React Native was the way to go. Even though the React Native technology was still in its infancy back then, we believed it would be a time- and money-saver. A few months later, React Native has proved its worth: maximum code reuse, live reload (enabling you to immediately see the result of the latest change that you have made to the code), modular and intuitive architecture and it’s superfast.

In the case of the Keytrade Bank project, two native apps (Android & iOS) were built over a 6-month period. Inconsistencies between iOS and Android disappeared and maintenance was much more simplified. Thanks to the React Native app, Keytrade Bank is ready to unify the workflow between its different teams, since they can use features covering backend, web and app at the same time.

The Keytrade Bank app is the first banking app built with React Native in Belgium. As pioneers, we learned a lot. Let’s highlight 5 lessons we’ve learned on the Keytrade Bank project.

1. Collect generic components

At the beginning of the project, go through the requirements and designs and make a list of generic or recurring components. After creating a few items, we quickly realised we could combine most of the items into 1 generic component.

Once you do that, and you talk to the product owner (PO) and designer to keep the designs in sync with the components you already have, you can create views faster than ever.

Another example is every Text field in the app. When we started we wrote something like this for every text :