Stack
Why this was the right shape
Mincha Alarm was intentionally smaller than a typical religious calendar app. The first version did not try to become a full siddur, calendar, community platform, or settings-heavy utility. It focused on one daily outcome: help a person know when mincha is relevant in their current location and remind them before they miss it.
That narrow scope made the product useful quickly, but it also exposed the real technical challenge: the app had to explain a time-sensitive calculation clearly enough that non-technical users would trust it.
Key build decisions
Location first, account later
The key input is the user's location, not a user profile. The experience asks for location permission because the zman changes by city and travel matters more than account history.
Zmanim explained in plain language
The public page explains that times are based on GPS, sunrise, sunset, and solar noon rather than hiding the logic behind a vague 'smart reminder' claim.
Multilingual from the landing page
The app includes Hebrew, English, French, Russian, Spanish, and Yiddish copy paths, with direction changes for RTL languages.
Auto language detection
A Base44 function detects language and stores lightweight page-visit context, so the landing page can start closer to the visitor's language without asking them first.
What shipped
- A public landing page with multilingual messaging.
- A phone-style notification preview showing the two important reminder moments.
- FAQ content around calculation method, offline behavior after setup, and halachic method support.
- Admin views for FAQ and contact-message handling.
What got tricky
- The product has to earn trust before the user installs anything. That made the explanation of GPS-based zmanim part of the product, not just marketing copy.
- RTL and LTR languages needed to share the same page without text alignment, ordering, and font choices making one language feel like an afterthought.
- The landing page had to communicate a technical calculation without overwhelming a user who only wants a reliable reminder.
What we would improve next time
- Add a small public demo that lets a visitor choose a city and preview today's mincha window before installing.
- Separate the calculation explanation into a dedicated article for people searching around zmanim, GPS, and travel questions.
- Track which FAQ questions get clicked most often so the product copy can answer real hesitation, not guessed hesitation.
Want a teardown like this for your own workflow?
Send the current process, the tools involved, and what keeps breaking. We can usually find the smallest useful build before anyone writes code.
Talk through a project