12 years of experience. 15+ apps delivered. One dedicated point of contact.
In short: I build iOS and Android apps for clients in San Francisco (873,965 residents) and across California. One single point of contact, 12 years of experience, delivery from concept to publication in 8 to 16 weeks.
My primary role is to protect your budget. Did you know that 80% of an app's features are never used (Pendo, 2024)?
From Bordeaux, I help my clients avoid this massive waste. With 12 years of experience on iOS and Android, I know exactly where the money should go. We cut the fluff to focus on what brings actual value to your audience.
The key advantage: an app that launches fast, tests the market, and costs the right price. It's a matter of logic. Let's build the essentials first.
You have a mobile app project in San Francisco.
And you are asking yourself the big question. iOS or Android?
Take a breath. Let's look at reality.
Android holds a 72% global market share (Statista, 2025).
That is massive.
Out of the 873,965 residents in San Francisco, the vast majority have an Android smartphone in their pocket.
If your customers use Android, you have no choice. You need to be there.
But careful. Making an Android app is not just ticking a box.
It is an ecosystem with its own rules. Its own design standards.
The most important factor is creating a smooth experience, no matter the phone brand.
Samsung, Xiaomi, Oppo, Google Pixel. Your app must run perfectly everywhere.
Building an app is not just writing lines of code in a basement.
It is a complete lifecycle.
We start with design. We do not draw randomly. We apply Android guidelines so the user in San Francisco feels right at home.
Then comes the code. We connect the app to your servers. We handle offline modes.
But the biggest part of the work comes after. Testing and publishing.
In short, publishing on the Google Play Store has become a real obstacle course.
Google has toughened its rules to clean up its store.
Today, for a new developer account, Google requires you to test the app with 20 different testers for 14 consecutive days.
No testers? No publication.
Then, you have to fill out the tedious data safety form.
Explaining exactly what you do with the user's location, photos, or contacts.
It is a question of trust.
All of this happens in the Google Play Console. It is the dashboard for your application.
I manage all this administrative and technical complexity for you. So your project launches smoothly in San Francisco.
I have guided dozens of clients over the past 12 years. And I know exactly what the number one fear is when launching an app project.
It is the fear of losing control.
You hand over your baby, sign an estimate, and then hear absolutely nothing for three months. You become entirely dependent on a technical black box. 🕵️♂️
The key advantage of our collaboration is total transparency.
It is a matter of trust. Even if I am not physically sitting in your office in San Francisco, you see absolutely everything that is happening.
To achieve this, we set up simple and highly effective workflows.
I do not use obscure technologies that will be abandoned in two years.
I use the industry standard, dictated by developer.android.com.
The key point is the longevity of your code.
Here is what I use under the hood of your app in San Francisco:
- Kotlin: This is the programming language. It is the engine of the car. Powerful, modern, and officially backed by Google. - Jetpack Compose: This is the bodywork. The modern way to build visual interfaces. It is fluid and fast. - Room DB: This is the local safe. It allows your app to work even when the user in United States loses their internet connection in the subway. - Retrofit: This is the mailman. The tool that fetches information from your internet servers to display it in the app. - Firebase: This is the control panel. Used to manage push notifications, user authentication, and analyze data.
No useless jargon with me.
Every line of code written for your business has a clear purpose.
A healthy technical foundation is the guarantee that you can evolve your project in the coming years without having to throw everything in the trash.
The worst mistake is coding for 6 months without ever testing anything in real conditions.
Take a breath.
Here is how we work together to launch your app in San Francisco.
First, we define the scope. We cut everything that is useless. We keep the essential.
Then, I develop. I deliver test versions to your phone regularly.
But the crucial step on Android is publishing on the Google Play Store.
It is no longer a magic button.
Google now requires 20 different testers to use your app for 14 consecutive days before you can make it public.
The most important factor is anticipating this delay.
During this phase, we fill out the data safety form. We prove to Google that your app respects privacy.
Once approved, we do not launch it to 100% all at once.
We do what is called a "Staged Rollout".
We deploy it to 1% of users in the California area. We monitor for crashes. If all is well, we move to 10%, then 50%, then 100%.
It is the only professional way to launch an app without risking a disaster on launch day.
Recently, I helped an e-commerce company that wanted to boost its local sales in San Francisco.
Their website worked fine. But on mobile, it was a disaster.
53% of users abandon a journey if loading exceeds 3 seconds (Google, 2025).
They needed a native Android app to build loyalty among their customer base in the California area.
In short, the goal was simple: make buying ultra-fast.
We developed the app in Kotlin.
For checkout, we integrated Google Pay directly and leveraged the NFC chip of Android phones to scan loyalty cards in-store.
That is the real power of a native app. Using the phone's hardware.
During the launch, we were very cautious.
96% of users who encounter a bug never report it. They delete the app silently.
So, I set up strict alerts on Crashlytics.
On the very first day in San Francisco, we spotted a checkout bug on a specific version of Android 11.
Immediate fix. Update pushed to the store.
Zero lost sales. The app now generates one-third of the company's total revenue.
I will not lie to you. Building a good Android app in San Francisco is an investment.
Often, we see that Android development costs 10 to 15% less than its iOS equivalent.
Why?
Because the development tools provided by Google are free and often more flexible.
Also, the Google Play developer account is a one-time lifetime payment. At Apple, it is an annual subscription.
But do not celebrate too quickly.
Let us pause for a moment. The key point is market fragmentation.
Making sure your app runs perfectly on a budget phone and a premium smartphone takes time.
A lot of testing and optimization time.
The budget depends on the complexity of your project, not a price-per-page formula. A simple MVP and a full system for the California area do not require the same investment.
What costs money is not typing on a keyboard.
It is the architecture. The upfront thinking. Error handling.
Every domain has its problems. Android often has the appropriate technical answer for your business in San Francisco.
It is the nightmare of bad developers in San Francisco. There are thousands of different screen models. My job is to ensure the design adapts perfectly to all of them.
Recently, Google requires 20 people to test the app for 14 days before publication. This is to eliminate garbage apps from the store in United States. I help you manage this step.
Kotlin. Java is the past. Kotlin is the official language recommended by Google. It is safer and prevents many silent bugs.
Yes, it will be in your name. It is a small one-time fee. You will be the sole owner of the app in San Francisco.
The most important factor is defining a threshold. We generally target the most recent 90% of users to avoid useless development costs.
No. Android has its own visual rules (Material Design). Copying the iPhone will frustrate your Android users in San Francisco.
It can take 2 to 7 days, in addition to the famous 14-day testing period. We must anticipate this in the schedule.
Yes, the work does not stop at launch. Android evolves every year; the code must be updated for your clients in the California area.
You do. As soon as the final invoice is paid, you receive all the source code developed for your business in San Francisco.
Absolutely. Android is very open regarding hardware usage: Bluetooth, NFC, GPS, camera.
While you hesitate, your competitors in San Francisco are moving forward.
The mobile world moves fast. Very fast. Today, 63% of global web traffic comes from mobile devices (Statista, 2025). If you keep pushing back the creation of your app, someone else will happily take your spot in California.
But be careful, do not confuse speed with haste. Launching an unstable application is the worst possible strategy.
In short: you have to act fast, but above all, you have to do it right. ⏳

15 minutes to start
Book →