Creapolis is a one-person studio. You talk to me, I answer, I write the code. No agencies, no translators, no handoffs. What I promise is what I deliver — and I deliver it myself.
Since 2019 I've been building software — at first as a studio, then as an obsessive hobby, and now as my job. I started with Flutter because I wanted to ship to iOS and Android without duplicating code, and I stayed in mobile because that's where you see if you know product or just throw features at the wall.
Backend was taught to me by Node. Infrastructure was taught to me by making mistakes. AI is being taught to me by hype vs. what actually works in production — I'm learning live, and I tell you what's worth it and what's not.
Creapolis is not a disguised agency. It's one person — me — who designs, codes, publishes, and maintains. If you hire me, you talk to me. If I deliver something, I wrote it. There's no team behind that's going to change the game mid-project.
It's not a straight line. It's years of mixing study, experimentation, and projects that sometimes went to production and sometimes died at commit number 47. Everything counts.
I started with Flutter looking for a stack that would let me ship to iOS and Android without duplicating effort. In parallel: Node.js for backend.
I began signing work under the Creapolis name. Personal projects, experiments, and first collaborations.
Pepinillo and Películas reached Google Play. They're not unicorns — they're honest product exercises: what happens when one person decides and builds?
The first own app conceived as a commercial product. iOS, Android, and web. Event management for LATAM. This is where the studio stopped being just code and started being product with real users.
Direct consulting, own apps in production, and several products in the oven. No middlemen, no agency, no handoffs.
None of these are revolutionary. All of them are rare in the industry. Here they are in writing so you know what to expect before hiring me.
I don't write a line until I understand the problem. If you can't explain why a feature exists, it shouldn't exist.
You talk to whoever writes the code. No project managers, no translations, no "let me ask the team and get back to you".
I tell you what I can and can't do. If I don't know something, I research it. If something can't be done, I tell you before billing you.
The brief is the starting point, not the Bible. I build what people will actually use, not what's written in a PDF.
This isn't a list of what I put on my CV three years ago. It's what I write this week. If it's not here, either I don't know it or it's not worth it.
If you're looking for a direct collaborator who asks before coding and responds the same day — we're on the same page.