This is the first article in a series about the updates in Caffeine V3; this piece will introduce the new build architecture. Stay tuned for the next one: how V3's design system creates more aesthetically pleasing apps.
If you've ever faced the situation where Caffeine, after 50 tweaks, forgot what your app originally looked like, here's the scoop on why that happened and why it won't be an issue moving forward.
In the V3 version, we've completely revamped the way Caffeine builds apps. Previously, Caffeine operated on a sequential pipeline, essentially a series of proxies running one after the other: planning the app, building the backend, building the frontend, running quality checks, and deploying. Each step had to be completed before kicking off the next one, and if the third step found issues with the second, there was no rollback.