Bathilde

Mobile Developer focusing on building my own projects like BreathInU and Ventilate

[Bathilde @bathilde_build]

Challenge before the end of the year: revive the website https://t.co/OsWbvLGIQp !

It has been live for a while but almost no traffic. Let’s change that 💪

[Bathilde @bathilde_build]

@stephenrobles @Maisomage Yess! It was approved last week:

https://t.co/RuVhJDMPTC

[Antoine v.d. SwiftLee  @twannl]

Super sad to see another conference go. FrenchKit, now known as Swift Connection, stops after 10 editions.

Conferences are more than tech: they make connections. I truly hope we’ll keep many of the other events 🙏🏻

[Bathilde @bathilde_build]

Daily App Store tip:

Your Review Notes are not a formality.

Think of them as a mini user manual for the reviewer.

Tell them what to test, where to go and anything they need to know.

[Bathilde @bathilde_build]

Las olas de calor urbanas dejan la noche más caliente que el campo. El asfalto suelta el día después del atardecer, y la ventilación nocturna empieza más tarde.

Cuándo abrir las ventanas en una isla de calor: 📷https://t.co/pejz6lx1JE

[Bathilde @bathilde_build]

Daily App Store tip:

Don’t bury your Privacy Policy and Terms of Use.

I always keep both links easy to find at the end of the App Store description.

Tiny detail, easy to forget.

[Bathilde @bathilde_build]

Autumn rain changes when to open your windows. Close before the shower, keep the blinds open for daylight, and air your home in the dry spells.

Ventilate reads clouds and rain.

📷https://t.co/I8xrZrGooc

[Bathilde @bathilde_build]

My biggest lesson after 10 years of shipping apps:

The technical work is only part of releasing an app.

You also need to understand review, distribution, marketing and your users.

And I’m still learning every day, so follow me to discover what I do!

[Bathilde @bathilde_build]

Daily App Store tip:

App approval is not the finish line.

Once your update is live, watch what happens.

Crashes.
Reviews.
Usage.
Retention.
Feedback.
That’s where the next iteration starts.

[Phillip Shoemaker @pbsIdentity]

If you have an Apple developer account or an app in the App Store, read this now and share it.

Apple rejects your app. The notice is vague, so you fix what you reasonably think is wrong and resubmit.

Apple approves it.

Months later, with nothing in review, Apple terminates your account under 3.2(f) for “a pattern of manipulative or misleading behavior.” Every app gone. No explanation of what you did.

Your crime? Trusting the approval.

Apple’s own reviewer looked at your fix, with your rejection history in front of them, and said yes. Then Apple turned that yes into evidence against you.

So who’s misleading whom?

I ran App Review for seven years and wrote the guidelines. 3.2(f) used to mean real fraud. Now it’s being used against developers who did exactly what Apple approved.

I’ve made this Substack post free for everyone. Every developer needs to see it before this happens to them.

Share it before someone you know gets that email.

https://t.co/mWa1oGRVFH

[Bathilde @bathilde_build]

Daily App Store tip:

Don’t wait until your app is approved to start marketing it.

Build your audience while you build the app.

By launch day, you want people who are already curious about it.

Follow me for more app-building and App Store lessons.

[Bathilde @bathilde_build]

@frankzinko Yess! Definitely worth adding them!

[Bathilde @bathilde_build]

Daily App Store tip:

Product Page Optimization and Custom Product Pages are not the same thing.

PPO helps you test versions of your default product page.

CPPs let you create tailored pages for specific audiences or campaigns.

[Bathilde @bathilde_build]

@hermanbjorheim Yes only the duo! Hopefully in the next few weeks it will be fine

[Bathilde @bathilde_build]

In the end I was not able to upload all iPhone duo screenshots last night, but the app has been send to review, still a win!

[Shital Shah @sytelus]

I don’t think people realize how selfless and wonderful the StackOverflow’s founders were.

Unlike reddit, x etc they insisted ALL of their content will be 100% open, nothing will ever be locked up in walled garden.

They made it a point by even offering structured data downloads!

They didn’t cared people cloning the website. They didn’t worry about putting the whole monetization thing at risk.

It was a true hacker spirit in it’s purest form.

Most folks won’t be able to grasp how hard this is. You are on top of the world. Millions of people depend on you daily. You have the rarest opportunity to rack in billions. And you still stay true to your principles.

This exactly in turn later enabled AI revolution. I still remember downloading entire SO archives and preparing it for pre-training while Reddit and others went onto lawfare and firewalling the content. Note that this was the content their users - not reddit employees - had created for free and voluntarily to help others and the world. But they locked it all up for profiting from it personally.

SO did none of that. I think they knew they will be sacrificed at the altar. Yet it will exactly serve the intent of their founding principles to help others and the world, now through AI, even at bigger scale.

All of today’s models are built upon efforts of such true pure hackers who spent their days and years to create training data for AIs. I was a proud SO contributer for many years and there are couple of times while testing models I did felt that models might have used my answers 😇.

Hats off to @codinghorror and @spolsky and so many builders and hackers at SO for moving the world forward, one revolution at a time 🫡.

[Bathilde @bathilde_build]

Great advices here!

[Frederick James @frederickjames]

A lot of new advice since I wrote this.

1. Avoid the 2nd pile at all cost.
If your first review is rejected, it'll go to a senior reviewer. You may wait 14+ days for another review. How to avoid?

- Keep the scope small! A few great features.
- Build native swift for less edge cases & bugs.
- No non-standard payment structures.
- Avoid gray areas: abandon offers etc.
- Submit these for review in a later build.

2. Get automated review.
The signals I've seen is that to have automated builds you'll need:
- An already approved app live.
- Lots of approvals in a row.
- Smaller, more frequent changes.
- Potentially swift builds are prioritised.
- It's on a per app basis.
- Build a trusted relationship with Apple.
- Revenue doesn't seem to matter.

3. Review Notes
Still super important. Real people are reviewing the first submission. So help them out. Record a video walkthrough of everything actually working. Don't hide anything, and NEVER mislead the user. That's what almost all the guidelines come down to.

[Victoria Ali @Victoriaaaaali]

We grew up with tiny worlds that fit in our pockets.

Now imagine opening one on your phone.

I’m building Pocketly — a cozy 3D dollhouse game inspired by the magic of Polly Pocket, designed for the iPhone Duo.

#iPhoneDuo #PollyPocket #Nostalgic #BuildInPublic

[Bathilde @bathilde_build]

@Maisomage I had an upload error in Spanish Mexico and Portuguese Brazil. After multiplied trying, I pushed the version anyway. It was already late for me

[Juanjo Valiño @juanjovn]

No me canso de decirlo:

A los programadores nos han arrancado de cuajo nuestra identidad de la noche a la mañana.

Que sí, que soy el primero en usar Codex o Claude Code.

Que sí, que shippear features a toda hostia, con las que antes ni soñabas, es dopamina por un tubo.

El problema no es el avance en sí, toda profesión evoluciona con el tiempo.

Pero es que en cuestión de 18 meses, todo lo que habías aprendido durante años, miles de horas de práctica, cientos de horas de estudio dentro y fuera del trabajo, se han esfumado.

Ya dan igual las discusiones sobre patrones de diseño.

Ya dan igual los libros de Uncle Bob.

Ya dan igual las noticias con las novedades en Swift.

Ya dan igual las horas debuggeando o resolviendo un problema que acababan en ese aha moment.

Hasta nos divertíamos cambiando el tema de colores del código.

Ya hace muchos meses que no toco una sola línea a mano, así que ya ni eso nos queda.

Nos hemos quedado sin identidad.

Como decimos en Galicia: A chorar a Cangas (supongo)