NativeScript and Frameworks: The Good, The Bad, and the Bitchy
Over the last 6-12 months, Raika has worked on a few different projects with a mobile app component and needed to build natively in iOS and Android. In the past, there have been projects designed to bring these two disparate platforms together by allowing programmers to construct a single code base and compile it to the native platforms before deployment. We research a bunch of different options (including Adobe’s PhoneGap and Google’s Flutter) and found that NativeScript gave us the most flexibility to create apps that were more complex and looked the most like code we were already comfortable with using.
Last year we posted our thoughts about frameworks as part of our “Buzz Words That Suck” series. We at Raika Technologies feel there’s far too much emphasis and reliance on frameworks in modern web and software development, and that often times these are used at the expense of or due to the lack of understanding traditional software development concepts and methodologies, like object-oriented, design patterns, and other fundamental skills and knowledge.
This week we are exploring the topic in a more in-depth way. Look for the podcast and the video blog (with our usual sarcastic wit, pop-up-video style) and let us know what you think.