For builders
FeelFamous is a human-first collection of AI and offline tools that communities can own and adapt. It is small, run by one person, and not trying to be a startup.
This page is for developers, ethical builders and anyone who might want to help. It says plainly what is stable, what is rough, what you can reuse, and how to get involved. Last checked 30 September 2026.
What the labels mean
- Flagship — the best current example of the work. Live and looked after.
- Maintained — works, and gets fixed when it breaks.
- Experimental — an idea being tried. It may change or disappear.
- Archived — kept for reference. Not looked after.
- Help wanted — a specific job someone could pick up.
Where to start
Make-Oid — a template to build your own
A small, working starting point for an AI identify-and-chat tool: upload a photo, get an identification, and chat with a character who knows the subject. Fork it, point it at a topic you know, and deploy it on Netlify's free tier. Written so an AI coding assistant can help you build the rest.
Be aware: it is a skeleton, not a finished product. The membership wiring in it is optional and may be out of date, so check it before relying on it. The identification quality depends on the model and your prompts, and it will sometimes be wrong.
Deploy it
- Fork the repository on GitHub.
- Get a free Gemini API key at Google AI Studio.
- In Netlify, import your fork. There is no build command, and the publish folder is the root. Add your key as an environment variable called
GEMINI_API_KEY. - Edit the places marked
CUSTOMIZE:with your topic and character. - Push to your main branch and it redeploys. Plan on roughly an afternoon, not five minutes.
Licence, in plain words
Make-Oid is AGPL v3. You may use it, change it and even sell what you build. If you run a public version, you must give its users your source code, including your changes, under the same licence. The README also asks that a business built on it gives 20% back to the community once it can. That is a request, not a condition of the licence.
Fish — a live example of the pattern
Identify a catch from a photo, or ask Captain Barnacle about fish, tackle and the sea. It shows how one of these tools looks and behaves once it is finished. Free to use, no sign-in for the main tool.
Identifications can be wrong. Treat them as a starting point, not a verdict.
The source isn't published yet, so Make-Oid is the part you can inspect and reuse today.
Jobs someone could pick up
- Testing the tools with a screen reader, switch access, smart glasses or a headset, and telling me what breaks.
- Improving Make-Oid's documentation for someone who has never built one.
- A current, simple example of membership or payments in Make-Oid.
- Reading the code for security problems. Please email me privately first.
How it's built
Static HTML with no build step. Netlify hosts the pages and runs small server-side functions. Supabase holds accounts and community pages where a tool needs them. Google's Gemini does the AI work. Keys stay in server-side settings and are never in the page.
What leaves your browser: a photo or question you send to a tool goes to Google's Gemini to be answered. Accounts and village pages, where a tool has them, are stored in Supabase. Payments happen on Stripe's own page. I don't run analytics, ads or tracking scripts on this site, and the fonts and QR codes are served from here. Each tool's page says what it does with what you send.
What AI can and can't do here: identifications and values are estimates and can be wrong. A tool never authenticates an item or guarantees safety. Every result says so.
What we try to hold to
- Privacy first. Collect as little as possible, and say so plainly.
- Offline where it makes sense. The travel pack is built to keep working without a signal, though I haven't tested that widely across devices. The other tools need a connection.
- Accessible. The aim is WCAG 2.2 AA. What has been checked: a Readable mode, colour contrast, keyboard skip links and phone-width layouts, tested in a desktop browser. What hasn't: real screen readers, switch access, smart glasses or headsets. That testing is a help-wanted job below.
- Honest about AI. It can be wrong. Values and identifications are estimates.
- Free tools stay free. Membership pays for hosting and upkeep. It doesn't lock the tools.
Ways to help
- Try it. Use a tool and see if it does what it says.
- Report a problem. Email the page and what went wrong. Please don't send passwords, keys or other people's personal details.
- Improve the docs. Fix what confused you.
- Fork the template. Build your own with Make-Oid.
- Build a village. A community page or tool for a group you belong to.
- Co-maintain. If you've done a few of the above and want to look after something with me, say so.
Get in touch
Email chris@chrisptee.co.uk. There's no form, no sign-up and no phone. It's one person reading, so a reply can take a few days. You don't need to share anything personal to say hello.