Android with Kotlin, iOS with Swift, Kotlin Native, flutter.io, React Native, PWA, Xamarin, Hybrid

Android with Kotlin, iOS with Swift, Kotlin Native, flutter.io, React Native, PWA, Xamarin, Hybrid - which way to go?

Currently there are tons of frameworks how to get your business model to the user... and in the app store

Full Native

Android with Kotlin, iOS with Swift
Deepest integration
Single way to make sure that you have no lock-in effect with a framework, and you are f**ed, when Apple or Google disallows the usage of a specific technology...
Two teams required
2x code

PWA (Progressive Web App)

Write offline- and push-capable PWA with web-technologies only
Some native features might require hybrid native development and bridging (like In-App purchases, AR, ...)
In best case:

One web team only for website and app
Maybe some native specialists for special features

Kotlin Native

Develop a shared framework with or without UI using Kotlin Native
Additional native code will most probably be required
Big Android team, small iOS specialists

flutter.io (React Native | Xamarin | ... )

One codebase (flutter: Dart, React Native: JavaScript, Xamarin: C#)

Additional native code will most probably be required

flutter.io is supposed to be the next default development platform for upcoming Android-successor Fuchsia - and has a good hype at the moment

Big flutter team with some iOS and Android specialists

Or enthusiastic native developers that want to jump on flutter

Hybrid

Mix of PWA, Web and Full Native where you choose e.g. on a screen or feature-wise level what to use with which technology
Mix of Web, Android and iOS specialists

How to make a decision from here?

There is no simple answer to this - the longer you are working with the technologies and teams, the more the context gets into focus rather than the technology itself. You should ask yourself: What is the most suitable technology for my context?

What are the planned features and which technologies are mandatory?
How can I standout from my competitors?
Which skills are in my team?
What budget do I have at hands?
How fast do I need to move - how much risk can I take (lock-in effect, dropped technology, development speed, quality, ...)?
How long-term do I have to plan?
Which crew/teams do I have at hands with which skills... and which commitment?

Freelance/internal?
Technical skills?

Do I have an app-only use-case or do I have to maintain a website as well?

After having answered those questions for yourself, head back to the stacks presented above - and choose your weapon.

What do we do at WELT?

Well, we have a full native team staffed already and our native apps have excellent ratings.

For Edition (iOS and Android) we have chosen to go for the (local) hybrid way - so the main application is native code but most of the views are WebViews, showing local HTML for performance and synergy reasons.

For News (iOS and Android) we went fully native, following the Server-driven UI principle:

We defined a design language with pre-defined, multi-purpose bricks, having the backend defining the screens and data
We shift as much as possible of the business logic to the backend, to avoid double implementation and staying flexible for changes without requiring to do another app release in the App Stores
We have a slighty bigger Android/Kotlin crew that takes care not only of the Android client, but also of the backend implementation using Kotlin with Spring Boot

We share a Kotlin lib with the Android Client and the backend
We are also trying to share the lib with iOS using Kotlin/Native but are not there yet

For us this works out quite nicely and we can move fast, adding more and more flexibility by shifting more and more dynamic logic to the backend.

For you it most probably is a question of your context

😊

Thanks to Anton Averin and Pawl Polanski for your input!

Comments

Most Favorite Posts

Server-driven UI (SDUI): Meet Zalandos AppCraft and AirBnB Lona

A short WTF: Joe Birch: SERVER DRIVEN UI, PART 1: THE CONCEPT Zalando seems to follow the SDUI principle as well - defining a common design language and construct the screens on the backend while displaying them natively on the clients. They even go one step further; they implemented a mighty toolset to enable non-technical stakeholders to define their own native app screens Compass: Web tooling to create screens and bind data Beetroot: Backend service that combines the screen layout definition with the data Lapis/Golem: iOS/Android UI render engines Crazy cool! Good job, guys (when you do an open-source release?) To even move faster a Flutter based UI render engine implementation was great! See also AirBnB Lona SDUI approach Building a Visual Language Why Dropbox sunsetted its universal C++ mobile project and AirBnB its React Native implementation

Judo App - Server Driven UI out of the box

Judo App Judo brings server-driven UI to your iOS and Android apps. Build user interfaces visually in a fraction of time and publish them instantly without submitting to the app store. Build Experiences - With No Code The Judo app for macOS, available through the App Store, is built for design professionals with common keyboard shortcuts and familiar concepts like canvas, layers and inspector panel. Workflow is streamlined with the ability to drag and drop media files directly into your experiences and manage your own Judo files in Finder. Manage Creative Execution A Judo experience is interactive and can include text, images, video and buttons. An experience may be part of a screen, a single screen, or more typically multiple linked screens. Judo supports screen transitions, carousels, horizontal scrolling and modals. Clients can add custom fonts and define global colors and these are updates applied universally. Effortlessly Deploy Judo Cloud syncs your experiences with your iOS and

Dark Theme (Dark Mode) in Android WebViews, WKWebViews and CSS

So your apps just implemented a shiny new dark theme and it’s looking 👌 There are lots of benefits to having a dark theme in your application, and having it consistent throughout your application allows for a great user experience. But what happens when the the user runs into a WebView in your app? Support: if (WebViewFeature.isFeatureSupported(WebViewFeature.FORCE_DARK)) { ... } Set: WebSettingsCompat.setForceDark(webView.settings, WebSettingsCompat.FORCE_DARK_ON) Current setting: val forceDarkMode = WebSettingsCompat.getForceDark(webView.settings) Joe Birch Assuming your question is asking how to change the colors of the HTML content you are displaying in a WKWebView based on whether light or dark mode is in effect, there is nothing you do in your app's code. All changes need to be in the CSS being used by your HTML content. CSS dark mode via :root variables, explicit colors and @media query: :root { color-scheme: light dark; --h1-color: #333;

Backend-driven native UIs

Backend-drive native UIs John Sundell Slide Share Using Back-End Design to Create Customizable Front-End Mobile Experiences By controlling the front end of mobile apps from the back end we can build customized experiences at runtime, creating cleaner interfaces and reducing load times. Nithin Rao UX Magazine The Hub Framework Welcome to the Hub Framework - a toolkit for building native, component-driven UIs on iOS ( no Android support released yet ). It is designed to enable teams of any size to quickly build, tweak and ship new UI features, in either new or existing apps. It also makes it easy to build backend-driven UIs. The Hub Framework has two core concepts - Components & Content Operations. Spotify LeeGo: Build UI without UIView LeeGo is a lightweight Swift framework that helps you decouple & modularise your UI component into small pieces of LEGO style's bricks, to make UI development declarative, configurable and highly reusable. Wang Sheng Jia

netfox - A lightweight, one line setup, iOS network debugging library!

A lightweight, one line setup, network debugging library that provides a quick look on all executed network requests performed by your app. It grabs all requests - of course yours, requests from 3rd party libraries (such as AFNetworking, Alamofire or else), UIWebViews, and more Very useful and handy for network related issues and bugs Implemented in Swift 2.1 - bridged also for Objective-C Start To start netfox add the following line in didFinishLaunchingWithOptions: method of your AppDelegate Swift NFX.sharedInstance().start() Invoke netfox UI Just shake your device and check what's going right or wrong! Shake again and go back to your app! GitHub kasketis/netfox

ImageOptim

ImageOptim optimizes images — so they take up less disk space and load faster — by finding best compression parameters and by removing unnecessary comments and color profiles. It handles PNG, JPEG and GIF animations. ImageOptim seamlessly integrates various optimisation tools: PNGOUT, AdvPNG, Pngcrush, extended OptiPNG, JpegOptim, jpegrescan, jpegtran, and Gifsicle. It solves too the Xcode bug: corrupt PNG file. ImageOptim

UIWebView no bounce

You can switch off the bounce effect of a UIWebView using this script: for (id subview in webView.subviews) if ([[subview class] isSubclassOfClass: [UIScrollView class]]) ((UIScrollView *)subview).bounces = NO; Considering the Apple Review process it may be problematic that we make assumption of the inner structure of the UIWebView - but some apps have made it through...

iOS & Android Development

Search This Blog