You have an idea and no codebase.
- Scope and architecture agreed in writing before a line of code
- iOS, Android and Web from a single Flutter codebase
- Shipped to both stores under your own developer accounts
Hector Waldman · Independent maker, Apps 369Flutter architecture, the backend behind it, the cloud it runs on, and the AI inside it. Six years shipping cross-platform products to real users — including my own, live on both stores.
Architecture and design system for a mental-health platform: state management, module boundaries, release pipeline and the front-end team's conventions.
Built and shipped Foodly alone — Flutter clients, Laravel API, PostgreSQL, cloud infrastructure, store releases and support.
Cross-platform apps, backends and AI features for products across the US, Europe and LATAM.
I am a senior Flutter architect and full-stack engineer based in Europe. I work in Spanish, English and Portuguese, and I have spent the last six years doing the unglamorous parts of shipping software: store rejections, migrations, release pipelines, and the call where you explain why something slipped.
I use AI heavily in my own workflow — for review, scaffolding and research — and I ship AI features inside products. It makes me faster. It does not make the architecture decisions.
"You will never receive an invoice you didn't see coming."
My own product, designed, built and shipped alone: a platform where restaurants publish digital menus, take bookings and run promotions, and where diners discover them nearby. Live on the App Store and Google Play.
















A call, then a written scope with what is in, what is out and what it costs.
1 weekData model, state management, environments and CI decided before the build.
1 weekTwo-week slices. You get a working build and a demo at the end of each one.
4–10 weeksStore submission under your accounts, then maintenance or a clean handover.
ongoingA fast, indexable site or landing page live on your domain in one or two weeks.
From an idea to a product in both stores, backend and cloud included.
Audit, stabilise and keep shipping a codebase someone else started.
A monthly plan: SDK and store-policy updates, crash fixes and small changes.
A second opinion in writing on structure, state, testing and delivery.
Authentication, roles, dependencies and secrets, GDPR and store privacy requirements.
Voice agents, speech pipelines and LLM features that ship, not demos.
First reply in under 24 hours, always from me. No forms that go nowhere.