Ship small, ship often
A working build every two weeks beats a perfect build in six months. You should be able to use the thing you are paying for while it is being made.
01About
JV Mobile Development is Jorge Valbuena. I build native mobile apps for founders and teams who need someone that can own the whole thing — not just the part that fits neatly in a ticket.
I have spent about nine years building mobile apps — first inside product teams, then independently. In that time the pattern I kept running into was always the same: the hard part is rarely the code. It is the decisions around it. What to build first. What to leave out. When to say the deadline is wrong.
So I work differently from an agency. There is no account layer between you and the person writing the code, because they are the same person. You get a direct line, honest estimates, and a build in your hands every couple of weeks.
Apple platforms are where I am strongest — Swift and SwiftUI for iPhone, iPad and Mac, with enough UIKit and AppKit history to work on apps that predate them. From there I build outward: Windows desktop software, websites and web apps, and the backends all of it depends on, so the pieces actually fit together.
One deliberate exception: I do not take Android work. I would rather be genuinely excellent on the platforms I know deeply than mediocre everywhere. If you need Android, I will tell you straight away and point you somewhere better.
I also take on rescue work: projects that were inherited, half-finished, or built by someone who has since disappeared. That work is unglamorous and I enjoy it more than I probably should.
iTrading Buddy is my own product — a trading journal for iOS. It is where I try ideas without a client's money on the line, and I write about that process on the blog.
02How I work
A working build every two weeks beats a perfect build in six months. You should be able to use the thing you are paying for while it is being made.
I reach for proven tools by default and novel ones deliberately. Your app should still build in three years without an archaeology expedition.
If a feature is a bad idea, or the timeline is wrong, you hear it while it is still cheap to change — not in a retrospective.
Design, code, release, and the messy parts after launch. Nothing gets dropped in the gap between specialists.
03Toolkit
Let's build something
Tell me what you're working on. You'll get a straight answer about scope, cost and timeline within two business days — not a sales sequence.