Processing the data into a UI state that is trivially 1:1 mapped to the UI makes a lot of sense and was very helpful at my past work. Just the sqlite thing is weird.
I'm copying a pattern used by Facebook Messenger where all UI state is stored in SQLite and the UI is a thin, pure function render:
- https://engineering.fb.com/data-infrastructure/messenger/
- https://www.droidcon.com/2019/10/25/the-light-way-2/
In the demo I can kill the app and re-open it in exactly the same place because the router state is stored in SQLite.
Discussion
No replies yet.