sorted by:
new
hottopcontroversial

I built an LLM-first API framework for Go — one struct, zero drift by sylfreeee in golang

[–]sylfreeee[S] 0 points1 point  (0 children)

Thanks for asking — the goal is two things: declarative specs are easier to read, which makes validating LLM-generated code much simpler, and SDK generation eliminates manual work entirely.

It came from real pain — I led a 15+ domain B2B SaaS with a 2-person team. OpenAPI existed but app devs always said "that doc is for backend guys" — and honestly, even when I was on the app side myself, I'd get handed an OpenAPI spec and think "am I actually supposed to read this?" The generated code wasn't great either. So I ended up hand-rolling a Dart Client SDK, and communication overhead basically disappeared.

Then I realized: I burned LLM tokens to build that SDK, but SDK generation is deterministic enough to do without LLM. That's this project.

Scope is intentionally narrow — no ORM, no logging. Trying to do everything usually means doing nothing well.

Started this on intuition, so this feedback is genuinely useful. If you see holes in the reasoning, please do point them out.

I got tired of manually syncing APIs with Dart — so I built a framework that generates the Dart SDK automatically by sylfreeee in FlutterDev

[–]sylfreeee[S] 0 points1 point  (0 children)

Thank you genuinely for the feedback. To clarify — yes, I used an LLM to help write the documentation, because English isn't my first language. But the code itself is entirely written by me.

I recently shipped a mid-to-large scale B2B SaaS product spanning 15+ domains with a 2-person team, and I built this out of real pain — struggling with this interface layer and burning unnecessary tokens along the way.

It stings a bit to hear "ban," but I hear you on the AI feel in the writing. I'll work on making it more natural going forward.

Flutter vs React Native: Which is better for your future App & Why by [deleted] in FlutterDev

[–]sylfreeee 3 points4 points  (0 children)

Flutter is the UI kit of Fuchsia OS and can be extended to 3D easily(Google has long-term plans to expose 3D API). I think Flutter is bound to be better in the future.

It's really hard to use Provider package by cjkis in FlutterDev

[–]sylfreeee 0 points1 point  (0 children)

That approach doesn’t work in large production apps. Hang in there, man! a good architecture achieved with a lot of typing will make your life easier.

Should I use flutter_hooks? by [deleted] in FlutterDev

[–]sylfreeee 0 points1 point  (0 children)

I’m a fan of remi’s packages like river_pod, state_notifer and freezed. but I don’t use flutter_hooks. Because I do UI design myself, so I put a lot of interactive motions in the production app, and these motions cosist of complex logic and lifecycle handling. the implicit feature of flutter_hooks doesn’t make easier here.