Basecamp 3 for iOS hybrid architecture #27
Description
After searching about Ruby Motion, a cross-platform framework for writing the ios/android/macOS app, I found this article from the basecamp blog.
The most thing which I like about this article is how they define what hybrid is:
First, it helps to be clear about what we mean by “hybrid”. That term is used in so many different contexts, that it’s almost meaningless. In our use, we’re referring to standard native apps where a significant portion of the content is rendered using web technology. I explicitly say content there because it is an important distinction. We’re not using a framework that attempts to mimic native controls using HTML/CSS. We’re not using a framework that tries to compile another language to native code, or make a cross-platform app from a single codebase.
They also show us the way to split the screen into the native parts or web parts. And using a lib named turbolinks to communicate between native and web.
Native or web isn’t a binary choice, but instead a spectrum:
ref: https://m.signalvnoise.com/basecamp-3-for-ios-hybrid-architecture/