#blockchain #btc #crypto #cryptocurrency #bitcoin #ICO #fintech#Ethereum #altcoin #ETH #crowdsale #token #tokens #tokensale#preICO #cryptomemes #cryptolife #cryptoporn#cryptocurrencies #ICOcoin #ICOtoken #bounty #bitcointalk#decentralized #trading #smartcontract #bitx #bitcoins #bitcoin
Once we agreed on the native approach we needed to decide with which platform to start and how to share the work done for one platform with other platform. We started to explore different approaches and technologies that would allow us to reuse the artifacts to some extent. As for now there is no magic technology that would allow us to convert Android app into iOS app or vice versa, therefore the approach we chose is to separate as much as possible the platform dependent code like UI from platform independent code like view models, business models and logic and data access code. And in such way we hoped that conversion of one language code base to another one could be be done faster. After exploring and comparing several approaches and technologies the several stood out among the others as the ones that work on both platforms:
1) Clean Architecture (https://medium.com/@dmilicic/a-detailed-guide-on-developing-android-apps-using-the-clean-architecture-pattern-d38d71e94029, https://github.com/sergdort/CleanArchitectureRxSwift)
The main idea was to make the platform specific code as lean as possible and shared code as similar as possible on both platforms. It would allow us easy and quickly convert the shared code from one platform language to another. It turns out that the solution structure, app layers and the idea of common code and platform specific code separation was similar to one used by Xamarian (https://developer.xamarin.com/guides/cross-platform/application_fundamentals/building_cross_platform_applications/part_3_-_setting_up_a_xamarin_cross_platform_solution/). The idea that we could speed up development just by using one common language in this case C# was very attractive. And therefor we decided to revise our decision regarding the native approach. We talked to other software development teams that have experience in delivering apps using Xamarin and the here is what they shared with us:
And once again we came to the same conclusion – the cross-platform benefits in our project will not outweigh the potential risks it could introduce.
Facebook (Customer dialogue, tips and community): https://www.facebook.com/fitradarme/
Twitter (News and views, customer service and experts): https://twitter.com/FitRadarMe
Linkedin (Industry insight, career opportunities and corporate values): https://www.linkedin.com/company/fitradar