Juno's free tools do the hard part of the pitch: a visitor rates their energy, adds sleep and heart-rate data and sees a spoon budget and a crash-risk flag, or times a 10-minute standing test against doctors' thresholds. Then the page says the plan "isn't saved or sent anywhere" and is lost when it closes; the only exports are copy or print. The call to action, "Let Juno do the counting", is just two store badges, and the download page shows nothing a desktop visitor can scan. Someone who just did the work in the browser has to start again from zero in the app.
First action
Define the fields each tool would pass and the in-app screen that receives them.
How to measure it
Tool-to-install rate
- Now
- –
- Target
- 8% of tool completions
- By
- 60 days
Steps
Map the fields
The result each tool shows: spoon budget, activities, readings, timestamps.
Founding Mobile Engineer 1 day
Build the link
Encode the result in the link itself so nothing is sent to Juno until the user saves it.
Founding Mobile Engineer 3 days
Handle first launch
Deferred deep link so a new install opens with the plan pre-filled.
Founding Mobile Engineer 1 week
Add the desktop QR
Show a QR code of the same link on wide screens.
Founding Mobile Engineer 1 day
Update the copy
Explain plainly what moves into the app and that nothing is stored before then.
Founder/CEO 1 day
Extend to embeds
Same button on the embedded tools on partner sites.
Founding Mobile Engineer 2 days
Measure
Completions, link opens and installs per tool each week.
Founder/CTO weekly
Why it works
Add a "Continue in Juno" button to the spoon calculator and the standing test. It builds a link that carries the result itself (energy rating, activities, readings and date) in the link, so nothing is stored on Juno's servers and the "nothing is stored or sent" promise still holds until the person chooses to save in the app. On phones the link opens the app, or the store and then the app on first launch, with the plan or standing-test log pre-filled as day one of their history. On desktop it shows a QR code of the same link. Do the same for the embedded versions on clinic and charity sites, then measure installs per tool.
The visitor has already invested effort and seen value; carrying that work into the app removes the blank-screen moment at first launch and gives their history a starting point. It also lets Juno measure, for the first time, which tools and pages produce users.
Ready to use
ChecklistTool handoff launch list
[ ] "Continue in Juno" button on the spoon calculator [ ] Same button on the standing test [ ] Result carried in the link, not stored on the server [ ] First-launch screen shows the plan as day one [ ] QR code on desktop [ ] Button in the embedded tools [ ] Tracking: completion, link open, install, day-7 return
Risks and how to handle them
Visitors worry their health data is being collected
Keep the data in the link, say so on the button, and only store it after they tap save in the app.
Deep links break on some devices
Fall back to a short code they can type in the app.
Evidence
- Your websiteSpoon Calculator: turns an energy rating, sleep, HRV and resting heart rate into a spoon budget and flags crash risk; the plan "isn't saved or sent anywhere", nothing is "stored or sent to Juno", there is no account and the plan is lost when the page closes, with "Copy or print it" as the only export; the closing CTA "Let Juno do the counting" shows only the two store badges.Source
- Your websitePoor man's tilt table test: a standing-test timer and heart-rate log that "reports your numbers against" doctors' thresholds; "nothing is stored or sent to Juno" and results can only be printed or copied; the app pitch reads "Want a record over weeks, not one morning?" with store badges, plus an "Add this tool to your website" embed offer.Source
- Your websiteDownload page /get: shows "Getting Juno…" and "If nothing happens, choose your store:" with an App Store and a Google Play badge only; no QR code, no send-me-a-link option and no web version for desktop visitors. The example report's "Create your report with Juno" button also goes to /get.Source
- HiringEngineering: a Founding Mobile Engineer (San Francisco, $130K–$200K, 0.5–1% equity) to own the app across "mobile architecture, AI, voice, health tracking, and performance" (React Native and Expo or native), and an AI Founding Engineer for conversations, health reasoning, retrieval, memory, evaluation and safety guardrails.Source