This is a small todo app to demonstrate how to separate application logic and business rules from Ionic 2 as a framework. Almost all the logic is in a directory called
core with no outside dependencies.
See Ionic 2 Todo app on GitHub.
Ionic 2 interacts with the
core app through a single point of entry, the
For a todo app, this example might be a bit over-engineered, but it serves as a starting point for a more complex app I’m developing.
Please read my other post Towards A Clean Architecture for Ionic 2 Apps to understand what I’m trying to achieve.
The app is extremely light on UI stuff. There’s basically a Timer that triggers a dummy interaction after 3 and 5 seconds. But that’s not the point of the project.
Continue reading Simple Ionic 2 TODO App
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