Allright! The main use cases are:
Embedded (Phoenix-based) mode:
- For existing Phoenix apps where you can’t or don’t want to fully migrate to Hologram
- To gradually adopt Hologram by adding components/pages incrementally within your Phoenix app
- If you prefer to treat Hologram as just the frontend layer while keeping Phoenix for the backend
- If you prefer staying within Phoenix’s ecosystem and conventions
Standalone mode:
- If you prefer simplicity - convention over configuration
- Goal is to be dead simple and “just work” out of the box
- The end-goal is ambitious: local-first features with a client-side data store that auto-syncs to the backend database, plus cross-platform development (web/mobile/desktop) using the same UI components from a single monorepo. The first standalone version will lay the basic foundation for this vision.
Edit:
See this newer post for a bit more detail: How should Hologram position itself in relation to Phoenix? (Poll) - #26 by bartblast
