I have one requirement for my new Ionic 2 app: The core needs to work without Ionic 2. It will be released as native apps for Android and iOS, but also as a Single-Page-App (SPA).
Ionic 2 is optimized for iOS and Android and not made for Web apps. Thus, I need to separate as much logic as possible from Ionic 2 and create a core application that can be interacted with through an Ionic 2 layer or an SPA.
This requirement forces me to think about a clean architecture when writing Ionic 2 apps.
I haven’t found the perfect solution yet, but stumbled across a few interesting ideas, concepts and articles that I want to share with you.
Even if you won’t make a Web-app, I hope you can take a few ideas from this post.
Continue reading Towards A Clean Architecture for Ionic 2 Apps
The other day I read on Hacker News something like:
I wanted to get into Web Development. Is it really that ugly, hard, and annoying?
I thought: What’s the problem? It ain’t that bad, but to be honest, it really is quite difficult.
Since I decided to make the new version of my app entirely hybrid, I’m intrigued by Ionic 2, Angular 2 and TypeScript.
Sure, you can punch out a stupid small app in no time with Ionic 2, but something with a bit more complexity requires a few more brain cycles. Obviously, my new app has to be maintainable, needs sync across devices, I want a web UI in addition to the mobile apps and all of a sudden, I find myself in the same mess as the guy who asked on Hacker News.
Doing a hybrid mobile app in 2016 means to learn:
Continue reading Hybrid app development is complicated