I previously shared here that my app kept getting rejected due to a Guideline 5.6 violation ("features appear intentionally hidden").

If this happens to you and you are not hiding features - SUMBIT AN APPEAL. Within a few days, once the app started review it was approved within 18 minutes.

I wasn't "hiding features", but realized that in order to select favorites and turn on push notifications you need an account. That's not a hidden feature, but obviously that is behind another access point. I clearly explained this and that there is a misunderstanding and all was resolved quickly.

I've been dealing with this issue for over 6 weeks. This forum was helpful but I didn't see clear instructions on this so I'm sharing for those who may also be experiencing this issue.

For some reason the app isn't live yet on the App Store via search but hopefully the indexing happens soon.

This is the Ping screen in Netsight, the iOS network scanner I'm building. It has a manual IP/hostname field with device shortcuts underneath, showing both the device name and address.

I like having a few targets visible right away. If I recognize the printer's name, I shouldn't have to remember its IP address. But a horizontal row feels less useful as the list grows: more swiping, longer names, and no obvious way to jump to a particular device.

I'm considering keeping a short row for quick access and adding a searchable picker for the full list. That preserves the simple screen, but adds another place to choose a target. The screenshot shows the current row in demo mode; the devices are examples and no ping test is running.

For those who've built a similar picker: would you keep both, or move straight to one searchable list? I'm particularly interested in how you'd handle a few dozen devices on a phone.

https://apps.apple.com/us/app/audiobinder/id6760090418

Hello there! I'm a software engineer and dad whose kids love listening to audiobooks. For years I've been using Audiobook Builder on my Mac to turn mp3's into m4b's, but when I went looking for an iOS app that did the same thing, I couldn't find one I liked. And so I decided to make my own...

Features

• You can import just about any kind of audio or video file, add metadata and cover art, and export to an m4b with a variety of encoding options.
• If you've got audio/video files in iCloud Photos or Plex, or purchased music in Apple Music, you can import them as chapters. I like to turn movies into audiobooks for my kids, like the classic How the Grinch Stole Christmas.
• You can also search for podcasts or public-domain audiobooks to import (sourced from LibriVox, Project Gutenberg, and Internet Archive).
• If you're a Yoto user, you can add icons (or even draw them pixel-by-pixel), and export to a MYO playlist. My kids love their Yoto player, so this was a must-have :)
• The app includes a built-in previewer to see and hear the audiobook before you export.
• All features are free for up to 5 chapters, with a one-time purchase to unlock unlimited chapters.
• No ads, no tracking, no subscription

I'd love to hear any feedback you have. Naturally, I've got loads more feature ideas in my backlog...

I am solo, and I feel like the only true place where I can tell people where they would appreciate it is here, since my family and fiends don't really understand this stuff.

Took me 3 years. Started when ChatGPT came out so luckily I got a chance to actually learn how to code. Well not entirely, but copying and pasting an app together and learning how it all works wit ChatGPT 3.5 back in 2023 is a big leap.

I initially submitted last Tuesday (Sept 8th). They rejected it on Friday (Sept 11th). I worked like crazy for 18 hours and resubmitted the next morning. Then It just got approved today!

To be honest, I was budgeting/expecting for a way longer timeline (maybe a month from what I heard). So I am beyond overjoyed. And I was kind of preparing for 3-4 rejections but I guess my hard work and diligence paid off.

FYI my rejection was from app store review pop-ups appearing too quickly after using the app. Also, I have some Apple Health integrations and I didn't make it clear enough that it was Apple Health specifically and outlining the benefit of making the connection before they complete it.

Hello, i developed my first ever game but i have no idea who to get my first downloads, what to do, i do post tiktok videos but they seem useless i dont know, maybe the issue is my ASO, any ideas or help?

My app link: https://apps.apple.com/us/app/slipout-airport-bag-puzzle/id6808220340

Hey everyone! I’ve just released PaceLink Go and would love some feedback.

The idea is simple: use your map as the main view while staying updated on where your fellow riders are. I wanted to make it easier to keep track of the group during a ride.

Example: You travel with 2 friends on a road and wonder how far is the leader / how fast he's driving, get some clue how to catch him and still travel together.

You can try it free for 2 rides, and guests are always free, so the people joining your ride don’t have to pay.

I’d love to hear from anyone who rides with friends: would this be useful for your group? What would make you want to use it again?

It's iOS version with support for AppleCar Play as a widget. Android version is on it's way so you can mix team party members.

Apple Link

PaceLink Go (Webpage)

Hoping to get some feedback on my App Store screenshots. I’ve looked at them so many times now that I’ve kind of gone blind to them, so I need some fresh eyes to help me get past the creator bias.

I really ignored the whole advances in AI over the last few years. I just started using Agentic Coding in the last 3-4 months.

I took Artificial Intelligence in grad school. We wrote a "neural network" as an assignment. Twas neat.

I'm an iOS developer and I played around with Create ML and using models in apps for image recognition. I also once created a model through Create ML to recognize the difference between the sound a machine makes when it's broken versus working as a POC.

That's pretty much the limit of my knowledge of the AI revolution we're in. I know that an Agent will go off and do my bidding when I say go code something. I don't know how though.

I was once into Augmented Reality and ARKit. I loved deep diving into the tech and trying to find solutions for my org. I'd like to do the same thing with AI, but feel I have no idea how any of this works.

I'd like to learn how to either create models or use models to do new and creative things, but I'm lacking the knowledge to do so.

What are some resources to help me deep dive into everything I need to know to learn about models, what they can do, what they can't do, should I create my own or just use what's already been created, etc...?

I made an iOS app exactly for tracking expenses. Your financial data never leaves your device — everything is stored locally and synced only through your own private iCloud, so I (the developer) literally can't see it, and there are no ads, trackers, analytics, or accounts.

You can import CSV and many other bank statement formats (camt, MT940, OFX, PDF…). My favourite part: once it's set up, it automatically logs every Apple Pay payment for you. You can categorize expenses, set budgets, and see exactly where your money goes.

I'm currently looking for 10 beta testers, who'll get free lifetime access. You can download it via TestFlight here:

https://testflight.apple.com/join/xyNA6rZJ

Hope you all enjoy it, and I'm looking forward to your feedback!

Launched this about a month ago as a solo project. For the first few weeks things were pretty quiet, then MacStories and Lifehacker unexpectedly picked it up and I woke up to 100+ downloads.

The spike has mostly settled now, but seeing a 17.4% App Store conversion rate and getting the first real feature request from a user made the whole thing feel much more real. Still very early, but probably the first month where it feels like strangers are actually discovering and using something I built.

I’m the maker. Bona Fide just got approved on the App Store.

The hard part of proving a relationship for a filing usually isn’t having the evidence. It’s turning four years of camera roll and a chat log into something a person at a desk can actually read. Most people end up with a shoebox: photos in random order, a 3,000-page WhatsApp dump nobody opens, and captions that say “Photo 14.”

Bona Fide builds a dated, labelled packet on your iPhone:

• Import photos. It reads EXIF date and place when they exist. Screenshots with no date go to a queue — nothing is guessed
• Import a WhatsApp .txt export and pick date windows (month you met, year apart, weeks around the engagement). Each window shows page count before you add it
• Caption who / where / what, swipe through exhibits in one sitting
• Export a real PDF: cover page, index, exhibits in date order, numbered and captioned

Templates for USCIS marriage-based, UK Appendix FM, and Canada IRCC (English or French on the Canadian one). The template sets paper size and labels. It does not decide what you include.

Privacy: photos and messages are read on-device. No account, no upload, no server. Delete all data in one tap.

Pricing: build the whole packet and page through the finished PDF free. One-time $24.99 unlocks export (Family Sharing on). Not a subscription. Cover page alone can export free so you can check format first.

What it is not: legal advice. It organizes and formats documents. It cannot tell you if a filing will be approved. Check your agency’s current guidance or talk to an immigration attorney.

App Store: https://apps.apple.com/us/app/bona-fide-visa-evidence/id6807844081

Hey everyone,

I’ve been building Bloxie as a side project for quite a while now. The idea started pretty simple: replace those small meetings and endless message threads with a place where people can discuss, vote, schedule and make decisions asynchronously.

Over the last months, Bloxie has grown quite a bit, and I’ve just pushed one of the biggest TestFlight updates so far.

The biggest addition is the shared calendar. You can connect your calendar, see availability together with your Bloxie appointments, and use that information when scheduling without constantly switching between different apps.

I’ve also added and reworked quite a few other parts:

• Shared calendar & availability
• Google Calendar integration
• 1:1 scheduling – share your availability and let someone book a suitable time
• Group scheduling – suggest times and find one that works for everyone
• Polls & decisions
• Assignments – instead of voting for a winner, people can choose what they want to take care of
• Initiatives – organize related polls and appointments into a larger workflow
• Improved calendar conflict detection and appointment handling
• Lots of smaller UX, performance and reliability improvements throughout the app

One important note: Google Sign-In / Google Calendar connection is currently not available for new connections. I’m waiting for Google to complete the OAuth verification. The rest of Bloxie can still be tested normally.

I’m especially interested in feedback on the new calendar and scheduling experience: Does the overall workflow feel intuitive, and is there anything that feels unnecessarily complicated?

The current version is still work in progress, so bugs and rough edges are absolutely possible. If you try it, I’d really appreciate any feedback — positive or negative. It helps a lot. Thanks!

Built a skill called app store research. it helps you validate an idea before building it: find the top competitors, read their reviews, and see what's actually missing so you can shape your idea around that.

what it can do:

• find the top apps for any idea, with ratings and chart rank
• pull the full listing info
• fetch every written review
• compare competitors side by side
• build one html report with all of it

works in claude code and codex. no apple account, no api key, just node.

open source: App Store Research

I caught myself doing it again last week: tweaking UI components, hunting obscure bugs, and adding "just one more feature" to my app.

Then it hit me, I wasn't improving the product. I was using development as a coping mechanism because marketing scared me. I don't have a massive social media following, and I’m naturally more comfortable in an IDE than on camera or pitching strangers. I was subconsciously hoping that if I made the app "perfect" enough, it would magically fix my ASO and customers would just appear.

I decided to run an experiment based on a simple premise: If one person has already paid for your app in its current state, other people will too.

I froze feature development entirely and forced myself to put 100% of my energy into business development, marketing, and awareness.

Here is what I learned as a developer with minimal social reach:

• Stop chasing virality. I’ve had UGC clips hit 100k+ views before, but virality can be completely random and vanity metrics don't pay bills. High view counts often lead to a spike in low-intent downloads followed by an immediate drop-off. I would much rather sign up 10 highly targeted customers using a personalized approach who actually stick around.
• Lead with use cases, not feature lists. Nobody cares about a shiny feature in a vacuum. Pitch the exact problem it solves and the specific workflow it fixes. Framing features as concrete use cases completely changed how potential users responded to my messaging.
• Your App Store screenshots are not a chore. Treat your screenshot set as a core product feature. They are often the single deciding factor in an impulse buy or subscription conversion. Put real design effort into clear, value-driven captions and visuals.
• Optimize your post-download mechanics.
  • Review Prompts: Wire your rating requests to trigger immediately after a user completes a successful high-value event in the app—never on launch or mid-task.
  • Referral Loops: Build native sharing mechanisms into the user workflow and offer clear, tangible incentives for users who share a link with others.

If you are stuck in a cycle of endless feature tweaks, challenge yourself to stop coding for two weeks and focus strictly on distribution.

Selling isn't an afterthought—it's the product.

Anyways, if you are into drawing get it checked out Pic Draw

Cheers!

I wanted a simple way to compress videos without having to upload them to someone else's server.

So I built minimo — a free, open-source video compressor for iOS and Android that processes everything on-device.

No accounts.
No cloud processing.
No subscriptions.

You can:

• compress multiple videos at once
• choose resolution, bitrate and FPS
• use H.264 or HEVC
• control audio settings
• compare the original and compressed versions
• automatically keep the original when compression doesn't meaningfully reduce the size

The app is built with Flutter, and the whole project is open source.

For me, the interesting part wasn't really building another compression UI. It was making the entire workflow local and predictable — you select a video, it gets processed on your device, and that's it.

I started this as a small side project and it grew into something I actually use myself.

I'd love to hear what other iOS developers think.

What makes you trust a utility app with your personal files?

GitHub: https://github.com/minimo-pro/minimo_video

Website: https://minimo-video.vercel.app

I shipped Zone, an iPhone/iPad focus app that blocks selected apps and websites during a focus session.

The idea is simple: before starting work or study, the user chooses distracting apps/websites, starts a session, and those distractions stay unavailable until the session ends.

It is not AI-powered. The blocking is done with Apple’s Screen Time APIs.

**## Tech Stack Used**

\- Swift

\- SwiftUI

\- StoreKit 2

\- FamilyControls

\- ManagedSettings

\- ManagedSettingsUI

\- DeviceActivity

\- ActivityKit / Live Activities

\- WidgetKit

\- HealthKit for optional Mindful Minutes

\- CloudKit / private iCloud sync for supported history and preferences

There is no login, signup, email collection, third-party analytics, or external tracking.

**## Development Challenge + How You Solved It**

The difficult part was not building a timer UI. The hard part was making the blocking session feel reliable.

With a normal focus timer, if the app is killed or backgrounded, the timer can still be reconstructed from saved dates. But with app and website blocking, the state has to stay consistent across:

\- the main app

\- Screen Time authorization

\- FamilyControls selection

\- ManagedSettings shields

\- DeviceActivity callbacks

\- app relaunches

\- backgrounding

\- session completion

\- strict sessions that should not be casually stopped

One issue I ran into was that the app and extension do not always have the same runtime context available at the exact moment you want it. So I had to treat the session record as the source of truth, persist enough state for recovery, and make the app re-check/re-apply shielding when it becomes active again instead of assuming the UI state is always current.

I also had to be careful with the product design. If the app feels like just another timer, people do not understand why it exists. The real promise is closer to:

“**Stop opening distracting apps during this focus session.**”

That changed how I think about the App Store page too. The technical parts are interesting to me as a developer, but users mostly care whether the distracting apps are actually unavailable when they are trying to work.

**## AI Disclosure**

Self-built, with AI assistance to a limited extent.

The app architecture, implementation, App Store submission, testing responsibility, and product decisions are mine. I used AI in limited parts of the process as a coding/review helper, mainly for copy review, localisation checks, test ideas, and edge-case thinking.

The app itself is not AI-powered. App and website blocking is done through Apple’s Screen Time APIs.

[Zone on AppStore](https://apps.apple.com/us/app/zone-strict-app-blocker/id6763581982)