Ali Husain Software engineer and product designer

01 Interface/Ethereal

Ethereal

Live app · open source

A calm coach for training, food and the shape of the day.

Ethereal on a desktop: the day as a timeline, with the next workout due in 23 minutes.Ethereal on a desktop: the day as a timeline, with the next workout due in 23 minutes.
Ethereal's guided workout player on a phone.Ethereal's guided workout player on a phone.
Ethereal's Today screen on a phone.Ethereal's Today screen on a phone.

An installable coach that plans the day, guides workouts and tracks nutrition, with no account and no ads; the plan and the diary stay in the browser. Designed, built and delivered end to end.

397
automated tests, 168 of them end to end
41
exercises, each one animated
1,474
foods, searchable offline
100
Lighthouse score on key pages, with an accessibility sweep against WCAG 2.1 AA

Why it exists

Most health apps do one thing and charge a subscription for it. Which workout to do, what to eat, when, and whether any of it is working is left to you. Most also want an account and keep your diary on their servers.

What it does

Ethereal plans the day around when you wake, eat and work, and shows the next step. It guides short home workouts with animated demos, keeps a food diary with a built-in food list, and smooths daily weigh-ins into a trend. It runs in the browser, works offline and needs no account.

How it is built

  • Your data stays in the browser

    Static HTML and JavaScript, no server code, no database. The plan and diary live in the browser's own storage.

  • Formulas as tested pure functions

    Every formula is a pure function with its tests beside it. The daily deficit is capped and the calorie target never goes below a floor, both in code.

  • A target that corrects itself

    The equations carry about ±10% error for one person, so every two weeks the app compares the weight trend with the plan and recommends a change of at most 250 kcal.

  • Exercise demos drawn in code

    Each demo is a jointed figure. A knee or elbow is solved from where the foot or hand must land, so planted feet stay still.

How I know it works

397 tests
229 unit and 168 end-to-end tests, on desktop and phone layouts, run on every push.
27 pages
An automated accessibility checker (axe) runs on 27 pages and fails on any serious violation.
1,474 foods
Each build checks every food for plausible values and that its calories are within about 12% of what its protein, carbohydrate and fat add up to.
48 frames
A test steps through 48 frames of every exercise demo and fails if a knee bends backwards. I added it after that bug shipped.

What was hard

Old pages after every deploy

The app uses a service worker, a script the browser keeps so pages load offline. A review found that after each deploy, moving between screens still showed old pages. The worker fetched fresh HTML only for full page loads; the in-app router's plain requests were answered from the cache.

My first fix also counted requests whose Accept header asks for HTML. It was not enough: the router sends no Accept header, and a second review caught that. What held: on this static site a path with no file extension is a page, and pages go to the network first, then the cache.

Limits

  • The numbers are estimates, not medical advice.
  • Your data lives in one browser. Clearing site data removes it, and nothing syncs between devices.
  • It cannot send push notifications, because there is no server.
  • No test exercises the service worker, because it is not registered on localhost, where the tests run.

Also in Interface

Open to remote work.

ali@gallowforge.dev