Product direction
Where NomadBadge is heading
NomadBadge starts as a PWA because it is the fastest way to make the guide useful on a phone. Native apps should follow real usage, not come first as a promise.
By Tim & Thomas 3 min read Updated 13 Jul 2026
1 PWA first
fast to ship, easy to improve
2 stores later
when the community signal is real
1 invite
bring one nomad who would actually use it
The short answer
Why start NomadBadge as a PWA?
The PWA is not a compromise if it feels fast, useful, and one tap away. It is the cheapest way to learn from real nomads now. Native apps should come when the guide has enough active people behind it to make the extra work matter.
The path
What has to happen before native apps make sense?
The product should earn app store work through usage, not vanity. The first version needs to feel great on the phone and prove people want to come back.
Start with a PWA that feels native
The first product goal is simple: open the guide on your phone, move around a city, and feel like you are using a real app.
Let the community prove the next step
A native app should follow real usage: saved places, field reports, repeat city searches, and people inviting other people because the guide helps.
Bring it to app stores when it earns the work
App Store and Play Store releases make sense when enough nomads would benefit from deeper phone integration and easier discovery.
Why inviting people matters
A native app is better when there is a living network behind it
This is the practical ask: if NomadBadge helps you, bring one person who would use it for a real workday.
App stores are useful. They make the product easier to find, easier to trust, and easier to keep on a phone. But they are not the first proof that this should exist. The first proof is people opening the guide in a city, finding a better place to work, and telling another person because it saved them time.
That is why the current ask is not vague growth. It is specific: use the PWA, add a real report when you can, and invite one person who travels with a laptop or needs better work spots close to home.
If enough people do that, native apps stop being polish and become infrastructure. That is the threshold worth aiming for.
Who belongs here
The digital nomad story has to get wider
NomadBadge should not look like one narrow travel stereotype. People work on the move at different ages, with different bodies, different backgrounds, and different access needs.
Remote work does not have one face.
A useful guide should feel open to a 22-year-old on a first trip, a 52-year-old freelancer, a wheelchair user, a parent working between errands, and anyone who simply needs a reliable table, outlet, and call-friendly corner.
The product can help with that by showing a broader picture of who remote workers are. Not just white, young, fit, solo travelers. Not just laptop-on-a-beach fantasy. The real version includes different skin tones, Asian, Black, brown, white and mixed communities, older workers, disabled workers, people with ordinary bodies, and people who work close to home as well as across borders.
This matters for more than marketing. If the product visibly belongs to more people, more people will feel invited to add the places that work for them. That makes the guide better.
FAQ
Questions people ask about the app plan
Is NomadBadge already a native app?
No. NomadBadge starts as a progressive web app because that is the fastest way to make the guide useful, installable, and easy to improve while the community is still forming.
Why start with a PWA instead of the App Store and Play Store?
A strong PWA lets us ship faster, fix real problems faster, and learn from travelers before spending time on native release work. The first job is a guide people actually use.
Will NomadBadge come to the app stores?
That is the direction if enough people join and use it. Native apps become worth the work when the community is clearly active enough to benefit from deeper phone integration.
How can users help make the native app happen?
Use the PWA, add real field reports, and invite one or two nomads who would actually use it. More useful contribution is the strongest signal that app store work is worth prioritizing.
Who is NomadBadge for?
NomadBadge is for anyone who works while moving around: younger travelers, older professionals, people with disabilities, people with different bodies, people from every background, and people who do not fit the usual digital nomad stereotype.
Read next
Use the current product, then bring one useful person
The next step is not abstract. Open the PWA, add it to your phone, and send it to one person who would actually test it in a city.
phone setup
Add NomadBadge to your phone Home Screen
Use the PWA today like an app icon while the community grows.
Open pagebuild together
Help build NomadBadge
How contributions and feedback keep the guide useful.
Open pageuse it now
Open the app
The fastest way to help is to use the current guide and add what you know.
Open pageOne useful invite
Help make the native app worth building.
Send NomadBadge to one person who would add a real field report or use it on their next workday away from the usual desk.