Yaelfiner.com

The save indicator went quiet: nothing when idle, a small spinner in flight, a checkmark that fades - only failure gets words. Checklist toggles became optimistic: apply locally, revert and toast if the write fails. And opening a post is now instant - the checklists load at boot with everything else, so the detail view is a memory read instead of a round-trip.

The pattern behind all three: the admin is the proving ground, the skill is where the lessons land. Three kit updates shipped alongside the app - a quiet SaveStatus, a new toast item with the snapshot-and-revert recipe, and a "load at boot, read synchronously" rule for store design.

The old model gave every WhatsApp/Facebook group its own message template and a day-of-week schedule, with a dashboard asking "which groups today?" That turned out to be backwards: Yael writes one message about a meditation and posts it to many groups the same day.

So now there are posts and groups. A group is just a registry entry - name, link, category, an optional allowed-days note. A post carries the message plus a checklist of groups, seeded by category or picked one by one, checked off as she pastes into each group. Categories moved from hardcoded values into the database so she can manage them herself.

Next phase planned: drafting the post copy itself from a meditation's transcript, adapted to the WhatsApp message format.

The positioning says the site should be built bottom-up from symptom pages - each chronic condition is a door into Yael's practice, all converging on a self-diagnosis questionnaire.

First round: 4 framework drafts (DPCG, AIDA, PAS, BAB) for a general landing page, using the copywriting skill's comparison process. PAS emerged as the natural fit for symptom pages because its structure (pain, agitation, solution) maps directly onto the symptom-door architecture - someone googles their condition and lands on a page that validates their specific experience.

Second round: 3 PAS variants for different symptoms (chronic back pain, chronic fatigue, insomnia) to test how well the template scales. About 40% rewrites per symptom (hero, dead-end treatments, case studies), 60% stays constant (structural argument, process, CTA, Yael bio). The template works but Hebrew quality degrades at scale - gender agreement on ambiguous verbs, invented word forms, English calques. Eli caught several that I wouldn't have flagged on my own. Automated Hebrew QA is going to be necessary before this scales to 10+ symptom pages.

Most shared links will go to people who don't have Yael's app yet, so the page they land on isn't a login wall for existing users, it's the front door for new ones. That's why it shows the meditation they were sent rather than a generic sign-in.

The path for a newcomer is now: tap the link, see the meditation's name and blurb, sign in with one tap, land in the player with the install banner, add to home screen. The iPhone quirk (links open in Safari, not the installed app) doesn't matter for this audience because there's no installed app yet.

A share icon on the player screen, and a share button in the admin once a meditation or lesson is published. It hands out the item's link and nothing else - the phone's share sheet on mobile, copied to the clipboard on desktop, where the share sheet has no WhatsApp Web in it.

The link already worked, but landing on it signed out used to mean a bare Google button. Now the login screen shows what you were sent: the meditation's name and blurb, and a line saying one tap and you're in. Sign in and the player opens right on that item.