Architecture, Maintainability, and Modelling
Decisions that keep apps adaptable and safe to change.
- The database is the skeletonWhy maintainable Bubble apps start with the shape of the data.
- Relationships, lists, and join typesWhen to get into a relationship, and when not to.
- States, statuses, and option setsHow to keep lifecycle rules out of scattered page conditions and workflow branches.
- Designing for change without overbuildingHow to leave future paths open without building a system nobody asked for.
- Knowing when to abstractAbstract shared meaning, not shared shape.
- Denormalisation and calculated fieldsWhen copied fields are worth the sync responsibility.
- Maintainable navigationA Bubble SPA navigation pattern built around route options and reusable state.