A visual tour of every screen in dminder, with design rationale and implementation notes. Choose your platform.
Pick any city — where you’re going on vacation, or home while you’re away — and dminder shows that place’s sun: its solar noon, its D window and its burn times, on its own clock. Planning a winter trip south? See exactly when the sun there will make vitamin D before you go.
That place’s sun, on its clock
Salt Lake City, picked from Colorado: solar noon at 12:13 PM local time, and its own D window.
Elevation counts
Higher places get stronger UV. dminder looks up each place’s elevation; tap it to enter your own.
If we can’t reach our servers
You keep your current place while the new one finishes by itself. If its time zone is unknown, you just pick the time it shows there.
Same on Android
Both apps share one engine, so a place gets the same sun times on every phone.
A place is saved only once its time zone and elevation are both known. A wrong time zone would put every sun time an hour off without a hint that anything is wrong, so dminder never guesses one from your phone.
Start a sun session, then keep using the app. Browse your history, check your progress, update your profile — your timer keeps running in a compact bar at the bottom of every screen.
Tap it to expand back to the full timer. Swipe the time display to toggle between elapsed and countdown. Your session is always one tap away.
Setting up a daily supplement used to open with a question almost nobody can answer: how many IU? The wizard opens with the question everyone can: what do you take? Pick your product and the label math is done for you — every IU value verified against the manufacturer's own supplement facts, never guessed.
One human question
The flow starts with something you actually know.
Pick your product
Label-verified IU per serving under every name. “Something else” keeps the classic form.
Servings, not arithmetic
Two tablets? Tap plus. The IU total follows the label.
Honest about missed reminders
You decide what an unanswered reminder means — because your blood-level estimate depends on it.
Why a wizard? Because a diary should never make you do label math — and because the difference between “assumed taken” and “confirmed taken” is real data, not a guess. The same product table and dose limits live in one shared core, so iOS and Android can never disagree.
Below 30° the sun makes no vitamin D. When it drops past that line during a session, the session ends at that moment, even if your phone has put dminder to sleep, and you get a notification right then: “The sun has dropped below 30°, so you're no longer making vitamin D.”
Ends at the crossing, not when you look
Phones pause apps you're not using. The session used to end whenever you came back to check it. Now it ends at the minute the sun crossed 30°, so History holds only the minutes that made vitamin D.
Says why
“Your D window closed at 1:48 PM” heads the summary. A session that stops on its own should never look like a glitch.
One rule, both phones
When a session ends (window closed, IU goal reached, time up) is decided in dminder's shared core, the same way whether the app stayed open, was in the background, or was relaunched.
A one-time prescription bolus — a Hidroferol ampoule, say — is a fact about today. A daily D3 softgel is a rule about every day. They are genuinely different things, so the add menu now lists them as two separate items: Supplement Dose for a one-off, and Set Up Daily Supplement for a recurring schedule.
Why this section exists. In 10.8.0, every supplement entry funneled into the daily wizard — so a user who logged a single prescribed dose got a recurring daily rule instead, one that re-inflated their estimate every morning and couldn’t be deleted from History. Splitting the menu back into two items, and giving the recurring rule a home you can reach, is the fix.
Two clearly labeled items
From the History + menu: Supplement Dose logs one dose today; Set Up Daily Supplement starts the recurring wizard. You choose which you mean before you ever type a number.
One-off: logged once, deletable
The Single Dose form records a dose on today’s date and nothing more. Delete it from History and it stays gone — there’s no rule behind it to regenerate the dose tomorrow.
Recurring: managed in one place
Every recurring rule lives under Settings → Daily Supplements, each with a delete control — so a schedule set up by mistake is always easy to find and remove, on both iOS and Android.
The rule of thumb: took it once → Supplement Dose. Take it every day → Set Up Daily Supplement, and manage it under Settings → Daily Supplements. iOS reaches the one-off from the Home +; Android from the History + — both offer both.
One line on your home screen with today’s best times to sit out — “Your ideal sessions today (MED20) are at 9:15 AM or 3:18 PM.” Computed for your skin type from real sky conditions, with the whole session kept safely under your burn threshold.
Tap through for the full day: time-to-MED and vitamin-D rate curves, your UV ceiling, and alternative plans — including a split plan that collects more D in two shorter sittings. Follow a plan and dminder reminds you when each window starts.
Every screen designed for OLED-friendly, eye-comfortable viewing. Follows your system appearance automatically — no toggle needed.
See all dark mode screensStart a timer on a cloudy day and dminder reads real-time cloud data — including separate low, mid, and high altitude layers — then sets your overcast level automatically. No more guessing with a slider.
Your vitamin D rate and burn time adjust instantly to actual sky conditions. On partly cloudy days, dminder even predicts when the sun is about to break through and sends you a notification.
High (cirrus) — 25% UV block
Mid (altocumulus) — 60% UV block
Low (stratus) — 85% UV block
Folded, the Duo is a narrow phone with its camera down the right edge, so iOS moves the tab bar to a rail on that side and every card stays clear of it. Unfolded, it is wide enough for the sidebar layout: your sections on the left, Home beside them, nothing stretched. The numbers are the same either way because both come from the same Rust core.
All vitamin D calculations, gauge math, MED algorithms, and D-level estimation run in a shared Rust core compiled to native code on each platform. The iOS app uses SwiftUI with the Rust library via FFI; the Android app uses Jetpack Compose with JNA bindings to the same Rust crate. The calculations are written once, not twice.