The browser and the desktop app should not compete with each other. They should do different jobs.

The web reader is for speed:

• open a passage quickly
• compare translations
• share the product easily
• let new users feel the value without a setup wall

The desktop app is for depth:

• Logos Chat beside the passage
• local AI with Ollama
• read-aloud
• offline-friendly study
• longer-form workflows that make more sense outside the browser

That split is useful because it matches how people actually approach Bible software. They discover and test in the browser. They settle into the desktop app when they want a steadier desk.

Keeping both surfaces aligned is what makes the product feel coherent instead of fragmented.