norosoa francia razafimahaleo

i made fuchcia smaller until it was right. It’s live.

By

no

Paris, the last week of June. My flat sits right under the roof. When the heat settles over the city, the room turns into an oven, and no one up here is knocking to see how the woman who can’t sleep is holding up. I’ve barely rested all month. Stack heatwave on top of chronic pain on top of deadlines, and the body files a complaint — mine did. I dropped some events I’d meant to attend. My pace fell through the floor. And we’re only at the doorstep of summer.

So, plainly: I’m worn out. Not for effect, actually worn out. I shipped regardless.

Before the quiet, here’s the full picture recap — what fuchcia turned into, why cutting it back made it stronger, and what these six months rearranged in me.

The plan got ambitious. Then I cut it.

My first blueprint reached far: a proper backend, cloud AI doing the heavy lifting, a launch sometime next year. I believed in every page of it.

Then I tested the prototype in Maze, did the maths on what it really takes to hold women’s health data responsibly, and made a hard call. I took the build down to its honest core, a local-first beta:

  • No backend, no database, no account, no password. Nothing to sign into.
  • What you log — pain, flares, the small notes — lives in your browser and stays on your device. It never travels to me.
  • Your doctor-prep summary is assembled on your own device and sent nowhere.
  • The insight inside the app is simple on-device logic, not a chatbot. When your pain trend climbs, it gently flags that a flare could be near and opens your First Aid Kit.

Less surface. A clearer promise.

Why the cut made it stronger

Put a French woman’s symptoms on a server and the law re-files them: they become special-category health data under GDPR Article 9. That single reclassification drags in HDS hosting certification, a formal data-protection impact assessment, and almost certainly a dedicated officer to own it. That’s the correct weight for health data. It’s also far past what one person can carry on a beta budget.

So I solved it by subtraction. Collect nothing, and there is nothing to certify, nothing to breach, nothing to hand over, nothing to sell. A product that forgets you the moment you close it is, in this era, the rarer kind of trustworthy.

The privacy isn’t sitting in a policy document — it’s soldered into how fuchcia is built.

A note to myself and to you

I keep a small running glossary, because using words precisely is a form of respect: for the reader, and for the work. Three entries matter this month.

Words for finishing — close cousins, not twins.

  • Produce: to bring something into existence. Plain English, nothing more. (Watch this one: “produce” is not “in production.” “Going to production” is an engineering term — pushing to the live environment real users touch. You can produce something that never goes live. Different beast.)
  • Ship: hand it to actual people. The release.
  • Deliver: supply the value you promised. The outcome, not the artefact.
  • Launch: announce it to the world. The moment.

A one-line test for each: Is it running live? (production) · Can a real person use it? (ship) · Did we tell anyone? (launch) · Did it actually help them? (deliver).

Six months of producing, one release to ship it, a single outcome to deliver: a woman who knows better her body, who handles better her symptoms and flares and reaches her appointment better prepared and a little less alone.

Words for the AI label — used carefully.

  • AI-native: designed around AI from the first decision; pull the AI out and nothing stands.
  • AI-embedded: a normal product with AI tucked inside particular features.
  • AI-assisted: AI helps me make it; the product itself may run no AI at all.

Where fuchcia honestly sits: the original vision was AI-native; the beta is AI-assisted in the making, and what runs inside it is plain on-device logic. I won’t dress that up as a model it isn’t.

Words for what you’re holding — four rungs.

  • PoC: proof the idea can work at all. Disposable. Is this even possible?
  • Prototype: a stand-in to test the design with real people; never production-grade. Is this the right thing, and can people use it?
  • MVP: the leanest real version someone can use, built to learn from. Will they use it?
  • MLP: minimum lovable product: an MVP people don’t merely tolerate but come back to. Do they care?

fuchcia moved from prototype (v5, tested in Maze) to a local-first beta aiming past usable toward cared-about. In a health space, being trusted isn’t a stretch goal. It’s the floor.

Who it’s for and what I mean by “migrant”

fuchcia is built for migrant women first. Let me pin the word down, since it gets loaded with things it shouldn’t carry: a migrant, here, is someone who left her home country and now lives in another country (France first). Nothing more. No politics inside it — just geography, and the long work of rebuilding a life inside a system that often can’t even say your name right. I’m not describing this from a distance; I left Madagascar and got my diagnosis here, in a language that wasn’t fully mine.

And it’s Malagasy and Filipina first — first, not only. I begin where I can speak with honesty: my own community, and the one next to it. Every other woman with endo belongs here too. She’s simply not my starting line. I won’t perform expertise in a story I haven’t lived.

On community — straight with you

I’ll be direct: I don’t sit inside endo communities myself. Group spaces aren’t where I steady myself, and if that’s true for you as well, that’s allowed. But plenty of women find genuine strength there, and I won’t bury that under my own temperament. So I’ll point you toward two independent groups inside the app (go to circle page). I don’t run them, I’m not a member, and I can’t stand behind everything posted in them.

The one ask I’m making

I don’t watch you. No analytics, no tracking, full stop. Which leaves exactly one way for fuchcia to learn anything: you choose to tell it. One short anonymous form, no email asked. It’s wired into the app — open fuchcia, go to about page and tap give feedback (anonymous), that’s the whole loop. This isn’t an extra. It’s the deciding step: roughly 20 to 30 thoughtful responses settle whether fuchcia earns the next build.

→ Try the beta: https://fuchcia.com/ · or open the form directly: https://tally.so/r/lbzNoo

Six months that reshaped how I work

For the recruiters and product people reading this, the part that’s about the craft.

I changed my method, not only my output. I brought MCP, workflows, projects and skills into fuchcia and into how I run my days. Because the labels blur, here’s how I use each:

  • MCP (Model Context Protocol): one shared standard that lets an assistant reach outside tools and data through a common port, instead of a bespoke hook every time.
  • Workflows: the steps I lay out in advance for the model to follow.
  • Projects: a workspace that holds the context for one body of work, so nothing drifts off-brief.
  • Skills: reusable instruction packs the assistant loads to do one job well: a clean document, a sprint review.

And to be exact about a word people stretch: I don’t orchestrate agents, not yet. An agent is a system you hand a goal and let run its own steps. That’s not my setup for now. I keep my hand on the wheel — I set the path, the model moves inside it.

I built my own training out of online courses. I didn’t follow a curriculum someone else closed; I pulled from courses online and assembled the one I actually needed. The rest of the learning compounded where it always does — in the building itself, and in the articles and podcasts I keep close.

Tools aren’t the point. Trying a lot of them and then keeping only the few that match how you think — that’s where speed comes from. Not a single magic app. A deliberate shortlist, and the nerve to drop the rest.

Junior on paper — not on this. My CV says junior. fuchcia says otherwise: I scoped it, built it, halved it on purpose, and shipped it alone. Six months ago the soundtrack was that “all by myself” mood — you know the track. By September I want to stand somewhere new, in full Burna Boy register: “tested, approved, trusted”. That’s my anthem for the season.

The rule underneath all of it: I do what I say. I say what I do.

Again. Founder? Not the word I’d use

I don’t call myself a founder. Maybe one day, maybe never — either way it’s fine. Builder is the truer fit.

Which brings me to the honest ask: I need a permanent role secured by the end of September. Product Builder, Product Owner or Product Manager. If you can genuinely help — really, not loosely — let’s talk.

This is my last post until September. The heat isn’t done with me, so I’m resting on purpose — choosing steady again over fast, the same way I build.

If fuchcia speaks to you, say so in the form. That’s the only data I’ll ever want.

Have a good summer!

— make it simple.

feel the heat-ChatGPT-2026-by no

sources / further reading

Posted In ,

Discover more from norosoa francia razafimahaleo

Subscribe now to keep reading and get access to the full archive.

Continue reading