Everyone's talking about MCP like it's the missing link for AI tooling.
I don't think it is. At least, not yet.
Useful? Sure.
Production-ready? Not even close.
MCP introduces a new layer you now have to secure, monitor, and debug. It relies on stateful connections, breaks serverless patterns, and opens up some scary security holes if you're not careful.
Don't fall for the "spec equals maturity" trap. It's okay to wait.
Sorry it came off that way. Not my intention, and to be more direct, I'm not hiding it and do not wish to. Sorry again about that.
Appwrite is fully open-source, which is a big reason I stand behind it.
My role is to represent the developer community and surface their needs, not build the internals. So when I say I like where Appwrite is going, it's coming from that perspective.
Yes and open about it. You can check my other HN posts, including the last one about Appwrite Sites, where I mentioned I'm a team member: https://news.ycombinator.com/item?id=44027691
I also build with Appwrite, so I experience it as a user. You might have noticed some of my products on GitHub, including https://nextjob.work
Thank you. I appreciate this and will try what you've mentioned.
If you have the time, please check out Faye's privacy policy and let me know if it's clear enough: https://faye.health/privacy-policy
My goal is to make it very transparent and easy to understand.
Oh, and about the app vs web page comment, I get you. However, it's a progressive web app and can be installed. Works offline too. If you check Faye, you'll notice an install button at the top right.
Thanks, that means a lot. On the insights side, Faye does give useful cycle predictions and analysis from logged data, and they're all generated offline.
There’s also an optional AI insights feature (using OpenAI API), but only if someone chooses to use it.
100% agree. It’s less "product-market fit" and more "husband-wife fit." Wasn’t trying to build a startup, just trying to fix something that felt broken for someone I love.
And since it’s free, Faye doesn't need mass adoption. It just needs to exist for that one person who goes, "hold on...my health data ended up where?"
Or for when the next data breach hits and people start searching for local-only options.
I'm in the UK. But I've seen developers from all around having the same issue. (See Reddit)
My app is a free app, and their policy (which I don't agree with) states that private home addresses will only be shown for monetised apps.
To my surprise, Google published my home address for a free app. My account is new too, and address verification is a requirement for getting your developer account approved.
I don't think it is. At least, not yet.
Useful? Sure.
Production-ready? Not even close.
MCP introduces a new layer you now have to secure, monitor, and debug. It relies on stateful connections, breaks serverless patterns, and opens up some scary security holes if you're not careful.
Don't fall for the "spec equals maturity" trap. It's okay to wait.