Full Time
$15-$20
40
Jun 24, 2026
I need a full-stack vanilla-JavaScript + React Native developer
to ship a suite of small cross-platform apps (web PWA + iOS +
Android).
The stack is deliberately lightweight:
- Pure HTML/CSS/JavaScript
- No build step
- No TypeScript
- Minimal dependencies
- Shared engine files run identically on web and native
- Offline-first PWAs
If you're someone who can't wait to "modernize" this with
Next.js, TypeScript, and a big framework, this role isn't for
you. I built it lean on purpose. I want a developer who's
RELIEVED by a minimal stack, not annoyed by it.
The work:
- Take small apps from working demo to shipped on App Store,
Play Store, and web
- 7 mini-apps in total, all structured identically — learn one,
the rest go fast
- Payment integrations: RevenueCat (native) and Stripe (web)
- Service workers, caching, install-to-home-screen
- Each app is intentionally small and bounded
How we'll start — paid trial:
You build (or finish) ONE small self-contained app in the
existing pattern. A few screens, the shared engine, the paywall
hook, an offline service worker. Real bounded task, paid at
your rate. Strong work leads to ongoing engagement across the
full suite of 7 apps.
I'm running a few of these trials in parallel with different
developers. Top performers continue.
Pay:
- Trial: $
and your rate)
- Ongoing: $15-25/hour, depending on your experience
- If you're senior and command more, tell me and make your case
WHAT I NEED TO KNOW ABOUT YOU:
1. Send links to 2-3 cross-platform or PWA apps you've
personally shipped. App Store links, Play Store links, or
live web URLs. Not "projects I helped with" — your work.
Without these, your application won't be read.
2. In one paragraph: tell me how you actually feel about a
no-build, no-TypeScript, minimal-dependencies codebase.
Be honest. If you'd push back on it, tell me when and why.
I'm not looking for the "right answer" — I'm looking for
YOUR answer.
3. Your experience with RevenueCat for native payments and
Stripe for web payments. How many apps have you shipped
with each? Have you handled subscription edge cases —
restore purchases, family sharing, grace periods, failed
renewals?
4. Walk me through one offline-first PWA you built. What was
the caching strategy? How did you handle conflicts between
offline and online state?
5. Tell me about a time a client wanted a feature you thought
was a bad idea (over-engineering, wrong tool, scope creep).
What did you do? What was the outcome?
6. Describe your current development setup. What other clients
or projects are you on right now? How would you fit this
work in?
7. What's your hourly rate AND your preferred trial pricing
structure (flat fee for the trial app or hourly with a cap)?
TO APPLY:
- Use a multiple of 7 Apply Points (7, 14, 21, 28, etc.).
7 is enough if your portfolio and answers are strong.
- Start your message with the word "offline-first"
- Answer all 7 questions. Skipping any = automatic rejection.
- Without shipped apps linked in your answer to Q1, I won't
read the rest.
Important notes:
- IP-sensitive project. Trial work requires a short NDA and
IP-assignment before I share any code. Standard, not scary,
but tells you I take it seriously.
- I will NOT ask you to do free spec work. Every trial is paid.
- This is ongoing work, not one-off. The right person could be
busy with this for years across the suite also doing upgrades and support.
About me:
I build evidence-first health and human-connection apps
(web + iOS + Android). The architecture is intentionally simple
and I want it to stay that way. I value developers who push
back diplomatically when something's wrong, but who don't
"modernize" things that don't need modernizing.
I respect expertise, pay on time, and have ongoing work for
the right person.
To apply: follow the instructions above carefully. Generic
applications will be skipped.