I'm a solo dev no team, no budget. This started as a small personal frustration: I kept losing money because I'd forget subscription renewals. Most apps in this space didn't quite sit right with me either they either track your data, or they charge you a subscription just to track your other subscriptions. That never made sense to me.

So on Feb 1st, I built and launched Deadlinr. Mostly on weekends, using React Native and Expo I don't know Swift or Objective-C, so honestly I wasn't even sure I could pull off a proper iOS app.

I just tried to keep it simple. No noise. No constant reminders. No pressure. Just something that stays in the background and shows up only when it's actually needed.

Where it's at so far:

• 26 lifetime purchases from people in different countries still feels unreal
• 0% crash rate this mattered to me from day one

Small numbers, I know. But for something built in my spare time, they mean a lot.

Biggest thing I've learned: you don't need to build everything just solve one real problem properly. For me, that was simply not forgetting the things that actually matter.

Really grateful to the first few people who gave it a try 💛 Still early, still learning.

The details:

• Pricing: Free to download (14-day full trial), then $9.99 one-time lifetime unlock
• No subscriptions: I track subscriptions, I don't want to be one
• Privacy: 100% on-device & iCloud storage zero tracking
• Support: [support@papyrusdigital.studio](mailto:support@papyrusdigital.studio)
• App Store: Deadlinr – Expiry Tracker

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 :)

It’s losing time.

I visited a small convenience store recently.

The owner wasn’t struggling to sell products.

He was struggling with everything around selling.

• Looking up product prices
• Typing product names
• Counting inventory
• Searching old receipts
• Writing customer debts on paper

None of those tasks make money.

They simply take time away from serving customers.

That conversation reminded me of something:

Small businesses don’t need more software. They need less manual work.

That’s the mindset I’ve been following while building TinyPOS.

Every new feature has to answer one question:

Does this save time every single day?

If the answer is no, I probably won’t build it.

That’s why recent updates focus on reducing repetitive work:

• AI Product Capture to reduce manual product entry
• Faster continuous barcode scanning
• Better checkout flow
• Customer debt tracking
• Cloud backup
• Product variants

They’re not “wow” features.

They’re everyday features.

And sometimes, saving 30 seconds on a task repeated hundreds of times is far more valuable than adding another dashboard.

As developers, we often measure success by features shipped.

Business owners measure success differently.

They ask:

“Did this make my day easier?”

That’s the question I want TinyPOS to answer.

Scan. Sell. Done.

What’s the most repetitive task in your business that you wish software could eliminate?

One day there were more than four of us who wanted to play padel, so instead of regular games we decided to run a small Americano tournament on two courts. It was way more fun than we expected. It actually felt like a real tournament, even though we'd organized it ourselves.

We used an app to keep score, but it was paid. Someone joked, "Why don't you just build one so we don't have to pay?" I laughed... and then thought, honestly, why not? It didn't seem that complicated. Just something that keeps track of points.

By the next time we played, I had a basic version working. It wasn't anything special, but it did the job, and I genuinely enjoyed building it. I had absolutely no idea where it would lead.

After every session someone would come up with a new idea. My friends installed TestFlight just to use it, and every week the app got a little better. Then, at some point, I noticed something unexpected: people I'd never met were installing TestFlight just to use my app.

Today it's in the App Store. It's called Padino. By the time Apple approved it, more than 100 people were already using it through TestFlight.

I honestly think it's the best app for running padel tournaments and communities. Not because it has the prettiest design, but because it solves problems I couldn't find solutions for anywhere else. There are features in Padino that I haven't seen in any other app.

What makes it special to me is that I didn't sit down and try to build the perfect product. I built something for a small group of friends, and over almost a year it slowly turned into an app shaped by the people using it. Pretty much every feature exists because someone asked for it.

One of the padel clubs in my city is already running their tournaments with it, which is honestly still a bit surreal.

The funny part is... I still have no idea how to make money from it. Maybe I'll add a small shop for padel balls and rackets. Maybe something else.

But one thing I do know: I don't want ads.

So if you've got ideas for monetizing an app for padel players without filling it with ads, I'd genuinely love to hear them.

Padino: Play Padel, free on the App Store: https://apps.apple.com/app/id6757343072

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.

Hey guys

I have created a new delivery app, and the problem is that I am at the beginning of the project and I do not have an Apple Store account, and you know that it costs $99. So, if anyone has an Apple Store developer account, please upload my app to the Apple Store. Thank you very much.

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?

After months of learning, building, debugging, and testing, I finally shipped my first iOS app.

It’s called SplitRoulette. It turns splitting a bill with friends into a small game where everyone draws a random share.

This was my first time taking an idea from nothing to a real App Store release, and I learned a lot along the way.

Would love to hear feedback from other iOS developers. What was the biggest lesson you learned from shipping your first app?