“The solution had to have a cross-platform output for both iOS and Android, so saving time by avoiding separate siloed app development was critical,” says Evan Payne, a Netcentric senior frontend software engineer. “The central data here originated from five different sources, a number that might increase in the future. Therefore, we had to pull that data into AEM, convert it all into the same format, then hand it back out in small bits to the app.”
The Netcentric team evaluated their development platform options including Ionic and React Native. They encountered “major issues with Ionic listviews getting out of sync,” says Payne, and veered away from React Native due to the development team’s “desire to leverage their Angular skills and develop both iOS and Android apps simultaneously.”
“We could work rapidly because of the combination of the familiar tooling along with a fast feedback cycle provided by the Apple and Google App Stores’ development workflows,” says Payne. “This speed also led to an excellent level of collaboration with Raiffeisen during the development process, and resulted in a polished app client going into production.”
The NativeScript community is rich with user code and documentation contributions, so the Netcentric development team leveraged Slack and Github when they had questions. They found the Slack community to be very helpful and with most of their issues already encountered previously, solutions were readily available. On other occasions, Github filled the void by validating issues between NativeScript and Angular.
“Another key factor for choosing to adopt NativeScript was the open source aspect and permissive nature of the license model,” adds Payne. “Netcentric became an active contributor to NativeScript source code through this model.”