What No One Tells You About Publishing Your First iOS App Solo

I shipped TRASH DAY to the App Store. It's live, it works, and I'm proud of it. But getting it approved the first time? That didn't happen. I got rejected—not because the app was broken or violated any guidelines, but because I hadn't given Apple enough to work with to review it.

Here's what I learned going through the submission process solo.

The First Rejection

My first submission came back rejected—and fast. I had a response within 24 hours. The feedback was essentially: Apple needed more information to understand what the app does and how it works.

The irony wasn't lost on me. I had already built a full marketing site at whenistrashday.com with a demo video, feature breakdowns, FAQs—the whole thing. I had put real work into explaining the app to potential users. But the App Store review process is separate from all of that. The reviewers aren't browsing your marketing site. They're working from what you give them inside App Store Connect, and if that's thin, the app doesn't move forward.

It wasn't a setback so much as a checklist item I hadn't completed. Once I understood what was missing, fixing it was straightforward. The second submission took about a week to hear back—so don't expect the same turnaround twice. Review times vary, and the second round was noticeably slower.

What They Actually Need

There are a few distinct things Apple wants from you, and it's easy to assume your marketing work covers them—it doesn't.

A review notes summary. Even if you have a beautiful landing page explaining your app, you still need to write a plain-language description inside App Store Connect that walks reviewers through what the app does and how the core flow works. Think of it like explaining the app to someone who has never heard of it and has ten minutes to evaluate it. What does it do? How does a user get from opening it to the key action? What should the reviewer actually test?

A demo video submitted to the review. I had a video on the marketing site. That didn't count. Apple wants the video attached to the submission itself, inside App Store Connect. Same content, but it has to live in the right place so reviewers can access it without hunting for it.

These two things were the main blockers on my first submission. Once I added both, the second submission went through.

One Thing I Didn't Have to Worry About

Because TRASH DAY collects almost no data and runs entirely on the user's device, I skipped a whole category of App Store friction. No account required, no sign-in, no data going to a server. Everything lives locally.

That meant no privacy permission dialogs to configure beyond the basics, no data collection disclosures to write, no account deletion flow to implement—all things that add real complexity to a submission. If your app touches location, contacts, health data, or requires a login, there's a lot more to fill out and justify. Mine didn't, and that kept the submission surface area much smaller.

It's a design decision I made intentionally and one I'd make again. Simpler for the user, simpler for me.

The Paid App Paperwork

Because TRASH DAY is a one-time purchase and not free, there was additional work on the business side before I could even submit. Apple requires you to complete your banking and tax information inside App Store Connect before a paid app can go live—agreements, tax forms, the works.

This isn't complicated, but it's not something you can skip or come back to later. If you're planning to charge for your app, get this done before you submit. It's a separate process from the app itself, and it takes a bit of time to fill out and process.

The Screenshots and Marketing Material

This part took the most time, and it's entirely on you as a solo developer. The App Store requires screenshots for every device size you support—iPhone, and if you're targeting iPad, those too. They can't just be raw simulator screenshots either. If you want your listing to look professional (and you do), they need to be designed.

That means picking a background, deciding on a layout, writing the headline copy for each screen, and making sure everything looks polished at a glance. I used the marketing screenshots I was already producing for the website as a starting point, but they still had to be sized and formatted to App Store specs for each device.

It's not hard work, but it's real work. And it's the kind of thing that's easy to underestimate when you're focused on finishing the app itself. Budget time for it.

The Honest Take

I want to be clear: none of this was difficult. The App Store submission process is well-documented, the tooling works, and once you understand what's actually required, it's just a matter of doing it. But as a solo developer, there's no one to hand off the business paperwork to, no designer to produce the screenshots, no one to write the review notes but you.

The gap between "app is done" and "app is on the store" is wider than I expected—not because any one step is hard, but because there are a lot of steps, and most of them only become visible once you're already in the process.

If you're building your first iOS app and planning to sell it, here's the short version of what I'd tell myself:

• Fill out your banking and tax info in App Store Connect before you submit—don't wait until the app is ready
• Write your review notes as a plain walkthrough, separate from any marketing copy you already have
• Attach your demo video directly to the submission, not just your website
• Block time for screenshots—one polished set per device size, not an afterthought

The app is out now. Go set your address at whenistrashday.com and stop missing trash day.