SoloEra solo activities, solo maxxing, sidequests, challengePoint at a pill and know what it is
Talk to Gian@gianmauric
Reach out if you want to build it, build it together, or just ask what they had in mind.
01 The idea
A loose tablet at the bottom of a bag, a blister strip with the box long gone, a relative's pill organiser nobody labelled. Point your phone at it and get the name, the strength and what it's for.
Pills are already identified by imprint code, shape and colour — pharmacists do it daily from printed reference books. It's a lookup problem with a visual front door, which is exactly what a phone is good at now and wasn't five years ago.
The second half is where the value is. Once it knows what you take, it can flag the combination: two medicines that shouldn't be taken together, a duplicate active ingredient across two brand names, a dose that looks wrong for the strength on the box.
Two hard parts, and one of them is not technical.
The database is national. An imprint code means different things in different countries, and generic manufacturers change appearance without changing the drug. It has to know which country you're in and admit when it doesn't recognise something, because a confident wrong identification is genuinely dangerous here — more so than in any other category.
And it must never advise. "These two interact, ask your pharmacist" is useful. "You can stop taking this one" is a product that hurts people and probably breaks medical device rules in most places. That line has to be drawn before the first line of code, not after a lawyer reads the app store listing.
Starts in one country where the drug register is public and machine-readable.
Generated build prompt
Your starting point. Copy it and start building.
Opens in your chosen app. Desktop app or sign-in may be required.
View full prompt
Build point at a pill and know what it is. Context: A loose tablet at the bottom of a bag, a blister strip with the box long gone, a relative's pill organiser nobody labelled. Point your phone at it and get the name, the strength and what it's for. Pills are already identified by imprint code, shape and colour — pharmacists do it daily from printed reference books. It's a lookup problem with a visual front door, which is exactly what a phone is good at now and wasn't five years ago. The second half is where the value is. Once it knows what you take, it can flag the combination: two medicines that shouldn't be taken together, a duplicate active ingredient across two brand names, a dose that looks wrong for the strength on the box. Two hard parts, and one of them is not technical. The database is national. An imprint code means different things in different countries, and generic manufacturers change appearance without changing the drug. It has to know which country you're in and admit when it doesn't recognise something, because a confident wrong identification is genuinely dangerous here — more so than in any other category. And it must never advise. "These two interact, ask your pharmacist" is useful. "You can stop taking this one" is a product that hurts people and probably breaks medical device rules in most places. That line has to be drawn before the first line of code, not after a lawyer reads the app store listing. Starts in one country where the drug register is public and machine-readable. Requirements: - Ship the smallest version that delivers the core value above, nothing more. - Pick a stack you can deploy in a day, and state the choice before writing code. - Handle the empty state, the error state and the offline case explicitly. - Pricing to build toward: Free to identify — that's the part people need at 11pm and nobody should hit a paywall for. $5/mo for a saved medicine list with ongoing interaction checks, which is the version a carer looking after a parent would pay for without thinking. Start by listing the screens, then build them one at a time.