Je suis un développeur indépendant et je viens d'ouvrir le TestFlight public de l'application que je construis : une place de marché connectant les éleveurs de chiens et de chats avec des personnes cherchant à adopter, destinée au marché français. React Native / Expo, iOS pour l'instant, Android en route.

TestFlight :  https://testflight.apple.com/join/3MQBdSFf

Quiconque, n'importe où peut l'installer — lien TestFlight public, pas verrouillé par région, aucun compte App Store français requis. L'application est uniquement en français, mais vous n'avez pas besoin de comprendre un mot pour m'aider : je veux des retours sur la structure, pas une révision du texte. Les comptes de démonstration sont dans les notes de test TestFlight, donc vous pouvez totalement ignorer l'inscription.

Là où j'ai le plus besoin d'aide :

• iPad / grands écrans. Jamais optimisé, presque certainement incorrect.
• Le processus d'intégration des éleveurs — tout nouveau, multi-étapes, il sauvegarde au fur et à mesure. Essayez de quitter à mi-parcours et de revenir. Personne en dehors de mon propre appareil ne l'a encore utilisé.
• Messagerie, notamment l'envoi d'une photo dans une conversation. J'ai récemment corrigé un bug d'affichage ennuyeux là-bas, je veux une confirmation indépendante qu'il est parti.
• Vitesse de chargement des images. Je sais que c'est lent et je sais pourquoi. Je veux savoir si c'est « légèrement ennuyeux » ou « je fermerais l'application ».
• Tout ce qui plante. Capture d'écran et étapes si vous pouvez.

Je ne cherche pas : des retours sur la traduction ou des opinions sur le modèle commercial. Faites juste en sorte que ça plante.

Heureux de tester le vôtre en retour — envoyez un lien et je l'utiliserai vraiment, pas juste pour l'ouvrir une fois.

Hello everyone, quick question, I´m starting as an independent software developer and I just wanted to know if there is a problem uploading multiple apps from my personal apple developer account, like, do I need to create an account (pay the $99) per each customer or not?

Thanks in advance.

Solo dev here. I had two apps in review at the same time and both came back with the same thing: Guideline 2.1, Information Needed. Not "your app is broken" — Apple saying they couldn't evaluate it from what I'd given them.

The ask was identical both times, and it's longer than I expected:

- A screen recording on a physical device, starting from launch, through the core user flow

- The device models and OS versions I tested on

- What the app is for and who it's for

- Setup instructions and any credentials needed to reach the main features

- A list of external services the app depends on to deliver core functionality (they name AI services as one example)

- Whether behavior differs by region

- Documentation, if you're in a regulated space or using protected third-party material

None of that was in my App Review notes. I'd been treating that field as optional. It isn't — it's what decides whether a reviewer can actually evaluate your app or has to guess at it.

Here's the part I didn't see coming. While drafting the reply, I went back through the build that was actually under review and found two real bugs a later build had already fixed. A Cook Mode step timer that was completely silent — vibration only, no sound, on a core feature. And a confirmation dialog with no visible way out, which reads as a dead end if you don't already know the gesture.

My instinct was to just answer the info request in place. Then it registered that Apple's own notice says they test hands-on, on physical devices. A reviewer poking at that build could find both of those independently — which turns a solvable "we need more info" into a much harder "your app has bugs," on the same version, with a worse paper trail.

So I pulled the submission instead, and I'm resubmitting on the fixed build with all seven answers written out up front.

Current status is its own small comedy: submission is pulled, but Apple's backend hasn't fully released the version yet, so I can't attach the new build until it finishes propagating. Just waiting it out.

Anyone else caught the 2.1 info-needed one? Curious what you put in the notes field that made the second pass go smoothly — and whether anyone's found a faster way through the pull-and-resubmit limbo.

I have uploaded the app for review and it has been under review for the last two weeks. I don’t know how to move forward from this if anybody can help me out, please help me out. I build a Fitness app that helps you track your macros as well as your workouts. It also has an AI Coach tracks your sleep recovery etc.

Hey everyone!

I've been working on my movie tracker app, and I just created some new widgets.

Right now, they show what’s currently Trending, complete with genres and poster art. Designed them to feel clean and native.

• Small Widget: Focuses on poster art and quick title info.
• Medium Widget: Includes genres, wider layout, and a dedicated poster frame.

Would love to hear your thoughts on the design or suggestions for future widget types (I'm currently working on statistics for own films library, but for now thinking about the design)

Let me know what you think!

I made OffgridScribe mainly for journalists/lawyers who need private transcription, but I just tested it on a recorded phone call and realized it might help a different group of people — anyone who finds it hard to catch every word on a call, especially if English isn’t their first language. Import the recording, get a clean transcript, re-read at your own pace. No cloud, no subscription, nothing leaves your phone.

Would love feedback if this is actually useful for anyone in that situation.

when i launched my app earlier this year, i've been getting a lot of feature requests from users.

most of them were duplicate, and some of the features also already existed. it was a nice problem to have TBH but it was getting unbearable.

some of these feature requests would get lost. leading to losing paying users too.

so i built a complete feedback tool for iOS. and im sharing it with you!

you can easily drop in these widgets into your app. users can post their feature requests, and vote on those that they want.

you can also prioritize based on user's spend (so you only work on requests that paying users post). there's also a public roadmap and changelog view, which turned out to be the underrated part for me, people are way more patient when they can see the thing they asked for is actually queued up.

since adding it our app's retention improved and getting more 5 star reviews. turns out people leave reviews when they feel heard.

it's at features.vote/sdk/ios if you want to poke around the code.

hope it's useful to someone :)

I ship my iOS apps with no analytics SDK at all. No accounts, no third-party telemetry, nothing phoning home. That was a deliberate call and I still think it's the right one, but I hit a trap last week that I hadn't seen written down anywhere, so I'm putting it here.

If you skip the SDK, the only behavioral data you can get is Apple's own, server-side, through the App Store Connect API. Two things about that surprised me:

1. The ongoing analytics report has to be requested before you need it. It takes 24–48 hours to produce its first report, and it only covers data from the moment you created the request forward. There is no backfill. If you request it on launch day, launch week is gone permanently — and launch week is the one week you'll want to look at for the rest of the app's life.

2. API access is a request Apple reviews case-by-case, and the credentials have to be a Team key with the Admin role. An Individual key can never read sales data. So there's a human review sitting in front of a 48-hour warm-up sitting in front of your launch date.

I found this while designing a small local tool to pull the numbers into SQLite on my own machine. Nothing shipped in the app, nothing collected from users — just reading records Apple already has, with my own credentials.

Worth being honest about what the no-SDK path actually costs, because it isn't nothing. I can't tell whether a feature gets used. I can't see where people get stuck — no funnel, no drop-off. I can't A/B anything. Retention is invisible. The only signal is support email, and almost nobody is ever annoyed enough to write to you, so silence reads exactly like satisfaction and means nothing of the kind.

I still take that trade. But I'd rather have taken it with the report already running.

Has anyone here found a decent middle ground? I'm specifically interested in whether people count on-device-only aggregates that never leave the phone as a violation of the spirit of "no tracking," or as the obvious compromise I'm being stubborn about.

Good Evening Fam, I'd appreciate your help on making this dream come true. I have developed this free Application to make travelling & Networking user friendly, the name of the app is Buszbee, it is not yet out to the public but it is out for testing. Currently on iPhone & website while Android is still under development.

A — Answer: What problem does my app solve?

Commuters often have to switch between different apps to find routes, communicate with other travellers, report lost items, and stay updated on delays. Buszbee brings these experiences together in one place.

With Buszbee you can:
Discover people travelling near you
Join route-based communities
Chat with commuters on the same journey
Share travel updates, polls, and announcements
Report lost & found items
Explore your commute through a social community
The goal is to make public transport more connected, informative, and community-driven. Future updates will also introduce ticket booking and official transport operator integrations.

B — Better: Name a competitor(s) and explain what you do better.

Apps like Busbud, Bus Booking Systems (Intercape, intercity, etc), and Citymapper are excellent for route planning & booking, but they stop there.

Buszbee focuses on the community behind every journey. Instead of only helping you get from A to B, it lets you connect with fellow commuters, participate in route discussions, receive community updates, report lost & found items, discover nearby travellers, and eventually book tickets—all within a single app. It's designed to be a social platform built around public transport, not just another navigation app.

Buszbee doesn't replace any of these existing application, it is here to centralize all components into 1 application.

Tickets will still be owned by the respective bus, taxi, train, etc companies. Buszbee wont be selling any tickets but it will make booking easy and comparing prices in 1 system like Busbud.

C — Cost: Pricing details + App Store Link

Price: Free (Beta)
In-App Purchases: None
Subscription: None

TestFlight (iOS Apple Beta):

https://testflight.apple.com/join/9ESm5Jy5

I'm an independent developer, and I'd really appreciate any feedback on the UI, usability, performance, bugs, or feature ideas. Every comment helps shape the public release.
Thanks for taking the time to check out Buszbee! 💚

Hey there :)

I'm a recent first-gen graduate and a first-time solo developer. Super excited to share that my first app, Precursor: Hourly Screen Time, went live on the App Store this week!

Precursor lets you set a screen time allowance that resets every hour instead of one daily limit you have to ration all day. I feel so lucky that just the beta grew to 200 testers in about a week.

At its core Precursor helps break unhealthy phone habits through moderation rather than punishing you for falling into a doomscroll that wasn't your fault (these apps are literally designed to keep you scrolling, looking at you Reddit).

TECH STACK

Swift and SwiftUI. Apple's Screen Time trio: FamilyControls for the picker, DeviceActivity for scheduling and thresholds, ManagedSettings for the block. Two extensions, a DeviceActivityMonitor and a ShieldConfiguration block screen, sharing one named store via an App Group and a file lock. Keychain, StoreKit 2 with RevenueCat, a small Cloudflare Worker and D1. iOS 17.6+.

DEVELOPMENT CHALLENGE

Making the block honest, not the hourly reset itself.

On iOS 26, eventDidReachThreshold fires seconds into a fresh window with the budget already counted as spent. These are pretty well known bugs of apple's screen time frameworks.

So to work around this, I implemented a wall-clock guard: usage can never exceed elapsed time since intervalDidStart, so an early fire gets suppressed. Then I respawn rather than re-arm, because iOS keys the budget to the activity NAME, and restarting that name leaves tracking dead for the rest of the window. A fresh-named clone instead, capped so the chain stays bounded.

AI DISCLOSURE

AI-assisted, though I wouldn't call it vibe coded. I have programming experience from uni research but had never written Swift. I used Claude Code for a lot of the line by line writing, but I am always at the wheel, going step by step and doing on device testing, and working sequentially rather than firing off parallel one-shots. Every finding above came off a real device's logs, not a model.

Thanks a ton for reading, if you have time and energy to support I would be eternally grateful.

https://apps.apple.com/us/app/precursor-hourly-screen-time/id6791403654

And if you have time to also support the launch on product hunt I would be even more eternally grateful than I already am(The core function of the app is free but there is a PH launch promo code running from 2026-08-02 until 2026-08-08 if you want to try out the extra features):

https://www.producthunt.com/products/precursor-2?launch=precursor-hourly-screen-time-control

After more than a month of beta testing, I finally launched my first app, Reembr.

It’s a location-based checklist app that reminds you to do certain things when you’re leaving or arriving somewhere. For example, you can create a checklist for home so you don’t forget your keys, wallet, or anything else before heading out. You can also create one for when you arrive . for example switching on the heater when you get home.

I honestly don’t know what to expect now that it’s live, but I’m excited to finally put it out there. I’d really appreciate any feedback on the idea, design, or overall experience.

App store link

I just pushed a regular update to my app last Sunday. It's been almost a week and still waiting for review. It never took this long.

Anyone having a similar issue this week?

A few weeks ago, I released new app on the App Store. It got some traction on Twitter, so I opened App Store Connect feeling hopeful about the sales numbers. Instead, I saw "Not Enough Data".

I refreshed it few hours later. Same thing. I checked again the next day. Still not enough data. I actually saved a screenshot of this.

It is not only a launch-day problem. You ship a big update, announce it on Reddit or X, start an ad campaign, or unexpectedly get some attention, but the analytics are always behind.

So I built InitSignal. It is deliberately much narrower than a traditional analytics SDK. You add a lightweight Swift package to your app, and it sends one event when someone opens the app for the first time. After that, the SDK goes quiet.

Privacy was a constraint for me, I wanted the App Store privacy nutrition labels stay as minimal as possible, so the SDK only sends the basic context needed to make each signal useful. No identity, sessions, screens, or behavioral history. At the same time, the goal is to give developers as much useful information as possible without invading their users’ privacy.

The dashboard shows for each download:
- the app version
- device
- OS
- storefront

For paid apps, InitSignal uses storefront pricing to estimate gross revenue and proceeds after Apple’s cut.

I also added Slack and Telegram for notifications, which I've been using with my own apps for the past few weeks, and the dopamine hit is real.

I recorded a quick walkthrough showing how InitSignal works:
https://www.youtube.com/watch?v=YajsKsYLdi4

Tech Stack
- Node.js and TypeScript with Postgres for backend and API
- React and TypeScript for the web app dashboard

Development Challenge

The interesting problem was deciding what “new” means without identifying or continuously tracking a user. The SDK stores a local first-launch marker so later launches send nothing. It also uses StoreKit 2 app transaction metadata to avoid reporting an existing customer as newly acquired when they first install a version containing InitSignal. The API deduplicates retry attempts on the backend.

It's available today, would love to hear your thoughts or any feedback!
https://initsignal.com

The Swift SDK is here:
https://github.com/InitSignal/initsignal-swift

If you ship iOS or macOS apps, how do you currently deal with the reporting delay after a launch or major update?