Fabrizio D'Urso

iOS and Android App Development

I've been doing iOS and Android app development since 2010, when I published my first app on my own. Since then I've published eight apps of my own, in Objective-C, Java, Swift, Kotlin and today mostly React Native, and built apps for clients. From the idea to the stores, and after.

What I can do for you

A new app, from the first version to publishing on the App Store and Google Play.
An existing app that needs someone to take it over: updated, fixed, moved to the latest iOS and Android versions. Even if someone else wrote it.
The part nobody sees: login, in-app subscriptions and payments, notifications, and the backend behind it.
Publishing on the stores, Apple reviews included.

Native or React Native?

It depends on what the app has to do. With React Native and Expo I write it once for iPhone and Android, and for most projects that is the right choice. When the app needs something tied closely to the phone, I write it in Swift and Kotlin.

I'll tell you once I understand the project, not before.

Apps I have built

Lumideo

My latest app: record a video today and choose the day it opens. React Native, Firebase, in-app subscriptions and a countdown widget.

App Store Google Play

Ruralis

The owners app, on the App Store and Google Play. When I joined there was little more than a draft.

Don Gaitano

A virtual Neapolitan «santone» who reads your dreams in dialect. Swift and Kotlin, with OpenAI and an ElevenLabs voice.

App Store Google Play

OutyPlay

Find people to play sports with near you. About 20,000 downloads, built and launched on my own. It is now closed.

Noon Happen

Dating that started from food and free time. Also closed today.

What I work with

React Native and Expo, Swift, Kotlin, and before that Objective-C and Java. Behind them: Firebase, Node.js and AWS.

Do you have an app to build or to take over?

Tell me what you need. In the first call we find out whether it makes sense to work together.

Let's talk for 15 minutes

Contact

Let's talk

Tell me what you want to build. I'll reply within 24-48 hours.

The questions you're asking yourself

I reply within the hour. When I start a project, I see it through. Whether I'm in Naples, Mexico or Japan, I work on European hours: within my working day, I reply within the hour. You know this before we start, not after.
It's yours from day one. The code on GitHub, server access, every project document: shared with you from minute zero. Not on delivery — right away. Which means the work carries on without me.
The price doesn't move. Once agreed, the price stays. Even if I got the hours wrong: my mistake, my cost. It changes only if what needs building changes, and in that case you hear it from me first — not on the invoice.
You're buying a date, not a file. A delivery date and something running in production. Not a file, not a zip: on the day I told you, it's live and you're using it. And from then on it's yours, because you've had it since day one.