Contract work · Daps Dev
I design, build, and ship software people actually use.
I’m Ivan Del Rio, the indie developer behind Daps Dev — a studio of iOS and web apps I’ve taken from idea to the App Store solo. I take on a small number of contract projects: iOS apps, web apps, and AI-powered products, engaged milestone by milestone so you always know exactly what you’re paying for.
- apps shipped
- 6
- live on the App Store
- 3
- handoffs — solo, end to end
- 0
Proof of work
Shipped, not slideware
Every app below is real, live software I built end to end — product, design, code, App Store review, and the legal pages to match.
yuckrBeta
The anti-Beli: rank the food you DON'T like.
ReceiptifyLive
Snap a receipt, tap what you had, split the bill.
CookedAILive
AI for the conversations you can't stop replaying.
SousEyeBeta
Cook from what's actually in your kitchen.
gymrotterLive
The rest timer that locks your phone between sets.
CardMaxBeta
Pick the best card to swipe — with the math.
Engagement model
How I work: milestones, not mystery
Every engagement is milestone-based. No open-ended retainers, no invoices for time you can’t see — fixed scopes, working software, and a payment only when you’ve accepted the result.
- 01
Scope, in writing
We break your project into fixed milestones before any work starts. Each milestone has written deliverables and acceptance criteria we both agree to — no vague “phase 2” hand-waving.
- 02
The first milestone ships real work
Never an empty kickoff or planning-only deliverable — the first milestone always includes working software, so you judge the work itself before committing further.
- 03
You accept, then you pay
Each milestone is invoiced when you accept its deliverables against the agreed criteria, within a defined window. You never pre-pay for work you haven't seen.
- 04
Repeat — or stop
Scope changes become new milestones instead of inflating existing ones, and either of us can end cleanly at any milestone boundary — you keep what you've paid for.
Ground rules
Engagement terms, in plain language
These are the ground rules every project runs on. They protect both of us and keep the work honest.
Written scope per milestone
Every milestone's deliverables and acceptance criteria are agreed in writing before work on it begins.
Acceptance window
Each milestone has a defined review window for you to accept the deliverables or request fixes against the agreed criteria.
Changes become new milestones
Change requests are welcome — they're scoped and priced as new milestones, so the current one stays predictable.
IP transfers on payment
Intellectual property in the deliverables transfers to you as each milestone is paid. What you've paid for is yours.
Confidentiality respected
Your ideas, code, and business details stay confidential. Happy to sign a mutual NDA before we talk specifics.
Clean exits, honest promises
Either party may end the engagement at a milestone boundary. Deliverables are warranted to match the agreed criteria — no guarantees of business outcomes beyond them.
This page is a summary of how I typically work, not a contract. Final terms for each project — scope, pricing, IP, and everything above — are set out in a signed agreement before work begins.
Start a project
Tell me about your project
A few sentences is enough to start. I’ll reply within 1–2 business days with follow-up questions or a proposed first milestone — one that ships something real.
- 1
I reply with follow-up questions or a call link.
- 2
You get a written first-milestone proposal — scope, deliverables, acceptance criteria, and price.
- 3
We start, and that first milestone ships working software.
Direct contact
boogie.delrio@gmail.com