A few years back, after building an iOS app called All Hours (no longer available), like most first time Indie Hackers from a developer background, I did no marketing and just built features. A winning combination that, as expected, found me launching with the sound of crickets.
... But, about a week into the launch, downloads went through the roof all of a sudden. I was so confused as to why, until I got a text from a friend saying it was on the front page of the (UK) AppStore. This was an incredible achievement for many reasons, with growth being the obvious one, but, for me, it meant I was one step closer to my long time dream of eventually winning an Apple Design Award. Years later, that day is still infinitely far away, so for now I will just drool at this post.
Shortly after this event, I had to give it all up and get a 'real job'. Because of that, for the longest time, I was unable to use and build upon this knowledge. But now I am back! And I am doing what I love, building great MacOS/iOS, with the hope that my up-and-coming apps, like SprintDock will get featured by Apple in the near future 🤞🏻
...So over the past few weeks and months, I have been dissecting other apps that have been featured by Apple and have abstracted what worked with All Hours. Now, I have to preface this post with the simple truth that even if you follow all these tips/suggestions to the letter, there is a high possibility that your app still won't get featured... sorry. Getting featured is still a numbers game, and we are all competing with thousands/millions of other Apps. But all of these suggestions will undoubtedly make your app a better experience regardless. So I hope you find at least one of these useful/insightful.
This one is self-explanatory. Don't build non-native apps, PLEASE! Apple wants you to use Swift which is optimised to run perfectly on all Apple devices. Plus, non-native is UX blasphemy.
This does not have to mean your idea has to be unique. Often, building on an existing idea is a safer move as you know the market exists. What this does mean however, is your app needs a wow factor!
This may come in the form of a super unique feature. It may be the simplicity of your UI/UX, an incredible onboarding experience or even just a super cool transition/animation. All Hours, for example, aggregated reviews into a super clean UI so that users could see reviews from both Google and Yelp, to present a better rating. This was not unique, but it was unique in its approach and UX/UI.
Now with SwiftUI, transitions and animations are easier than ever to achieve. This was not the case when I was building All Hours, but I knew many of the most impactful apps on the AppStore utilized animations so I spent a lot of time on the way each of the tiles transitioned into a detailed view. This, I believe, created a small but effective 'wow factor.'
That being said, animations, if overdone, can harm the UX experience more than benefit. So go easy on the rotating flashing views copied from your old MySpace page.
With everything I build/design, I try to see if anyone has done it before me and if so, how? Look at what works, what is already tried and tested.
I highly suggest looking at past winners of the Apple Design Award, as these are, in essence, what we are trying to achieve. Outside of that, there are plenty of places online to find great inspiration. For instance, I look at Dribbble daily for ideas. This has helped me immensely in finding ideas on how to approach a feature. For example, this Dribbble post from Golo gave me the idea of having a progress bar for the events within SprintDock.
I read a post a few months ago from an individual that was criticising anyone who didn't use a signup functionality when the app is initially launched. The need for capturing user metrics and getting a user to signup has its advantages. But it also has very clear disadvantages, as many people do not want to hand their personal information over as soon as they launch an app. More importantly, Apple stands with so many other data conscious users and their recent policies and privacy-focused features have made it very clear that Apple frowns upon apps that harvest unnecessary user data.

Think about which metrics are most important for you to capture. Less is better. But, if you do need to have a signup screen, for example, you should demonstrate value first, maybe with one of your 'wow factors'. A user does not owe you anything! It is your job to explain why they should hand over their email address/phone number/name to you. Give them a valid reason to do so, and be transparent with how it's used.
One of the best examples I have seen of demonstrating value upon initial launch was the trading app Robin Hood (before it fell from grace). When the user first opened the app, they could buy shares using fake money and see how the entire process worked before committing to anything. This demonstrated the value of the app and, along with helpful tooltips, gave people a reason as to why they should signup.
The AppStore is now available in 175 countries and most locales have their own team of curators. This is such a simple and incredibly affordable way of not only vastly expanding your market share, but also increasing the chances of getting featured as you have more Apple eyes (curators) on your app from different locales.
Just this weekend I, used Fiverr and other sources like Ideal Translation to get the SprintDock website translated into Italian, Spanish, and Portuguese (to begin with). Each translation usually costs less than $50.
Another simple, but sometimes overlooked, way of increasing your audience is to add accessibility functionality in your app for individuals who may have auditory, physical, cognitive, speech, and visual functional limitations. Your app should be accessible to everyone who wants to use it!
Apple has made note of developers that do this in previous Apple Design Awards. With the continuous push for accessibility API's and accessibility-focused features, it's obvious how important this subject is for Apple. But it should be extremely important to you too.
Speaking of using Apple API's, it's highly likely your app may require access to certain permissions to use it, like Push Notifications.
Don’t just trigger this permission request when the app launches for the first time. You should, again, demonstrate value as to why the user should allow your app to send notifications, and why your not going to tell them on the hour every hour about your one-off 15% off IAP.
Nobody wants to see an error, but when they do make sure it's concise and clear to a non-technical user. Add context as to why they are seeing it and style it appropriately, using animations and icons. For example, if permission has been disabled by the user, present the user with a reason to enable them again with a CTA to iOS permission preferences.
Localizing errors can't hurt either.
We've already established that you should use the first-party accessibility API's, but should you use the rest? Absolutely (if it fits of course)! Apple is known to highlight apps that utilize its latest and greatest features because it's a great way for them to showcase those respective features. It's a win-win for all.
I watch every WWDC and the in-depth tech presentations that talk about these new features, and try and think about how to utilize them. Can iOS Widgets, for example, help create your 'wow factor'?
One successful example of this is WidgetSmith. The founders of WidgetSmith saw their opportunity to build an app that focused on the newly announce widget API. They were one of the very first to do it well, and because of this, they were showcased by Apple on more than one occasion.
I know I said this one already, but I know some of you are still wanting to build your fancy web pages. Put the Javascript down dude, it's not worth it!
I know this is a cheesy way of signing off but bear with me. Apps made with a passion to create something great instead of just for the sole purpose of having an app, do stand out. At least they do for me and I know for many others, including people at Apple.
My name is Joe Barbour. I have been developing for iOS & Mac over over 10 years. I gave up the daily grind 6 months back to become a Indie Hacker & Solo-Founder and am #BuildingInPublic on Twitter so drop me a follow and DM me or comment below if you have any questions or hot takes.
Hey Joe, thanks for sharing these great insights! If you are comfortable sharing, I'd love to know — what happened after your feature?
Thanks for your wisdom and input!
Dave
Hey Dave. Thanks for the nice words. Unfortunately, due to personal and financial reasons I had to pull the app off the AppStore just a week later. I wrote about that in a little more detail here
But the over the week it was on the AppStore I recall it having around 2k downloads a day from about 20k impressions on the AppStore page.
I hope that is of some use. Apologise I cannot give you exact numbers.
Thanks Joe, that additional context helps a lot! And also learned from the other post you shared - so thanks for that. Best of luck, with all your introspection and reflection sounds like you are bound for success!
Great post Joe!
I 100% agree with the no-signup thing. If your app doesn't need to handle data for the core functionality, don't add a signup screen for the love of God! If people want to use it across devices they can always signup later in the settings.
Like the post, will create a checklist out of it. Is there any way you can influence the process? Reach out to them?
Unfortunately not, unless are a major player in Silicon Valley there doesn’t seem like there is any way of swaying them.
TBH, it is risky to hope the app to be featured by Apple so that the app is a success.
There are millions of good apps in stores. Getting featured is like hitting the lottery. There are just too many factors out of app developers' control.
Getting featured is excellent. There will be a spike in download numbers and revenue. But, such hype will be over as time pass. What are we going to do when excitement is over? Hoping the app be featured again?
In my 2cent, I think a more sustainable way is to optimize everything (app quality, app store page conversion, paid marketing acquisition cost, ...). The goal is to ensure the revenue is greater than the marketing expense. With such, this will ensure the sustainability of the app for many years.
We should celebrate when the app is getting featured by Apple. But, being featured itself shouldn't be a business goal because the outcome is not sustainable.
I couldn’t agree more. As I mentioned in the post, all of these things will still unlikely result in getting featured, but each will make your app better.
How can you be so sure that Apple won't feature non-native apps in the App Store? Just curious since I've made some stuff in React Native.
I cannot be sure of any of this as it's not documented by Apple so it's all just speculative.
But based on Apple's push of Swift and the performance advantages that it has over non-native languages and frameworks. Combine that with decades of Apple prioritizing it's own products and services and generally not playing nice with others. I'd say it's highly unlikely they would feature a non-native app. But I'm happy to be proven wrong.
@thebarbican great info! I'm actually about to submit my first app to the app store! What's your thoughts on going through the IAP-subscription through the app store vs just making it available through your website (netflix model)? If you was starting from scratch what would route would you take and what are the pros-cons in your opinion?
Firstly, congratulations! That is a huge step and I would love to know more about it.
Great question. I would always opt for the Netflix model as the 30% commission Apple takes is just outrageous . But as we are talking about been featured then if you choose that route, the likely hood of been featured by Apple drops dramatically which is Apples way of punishing anyone who refuses to give them their meaty cut.
I personally am going to be releasing SprintDock on the AppStore with an IAP. However, I will be also be offering it as a stand alone download from the website. I will not be advertising the AppStove version at all. The only reason for releasing on the AppStore is for the potential opportunity to be featured.
I hope that answers your question.
What about PR? I personally know about some apps that became featured via PR blasts and (sometimes) paid users.
You’re absolutely right. To be honest PR is just outside my area of expertise, which is why I didn’t mention it.
Gotta say I disagree with the "Native only" part.
I get it for the Apple featuring, but having built a business where I had to have 2 different dev teams for Android and IOS, it such a nightmare on a smallish budget. With the headaches associated with testing, marketing limitations and feature parity, I'm all for cross-platform frameworks now.
I think we are talking about 2 different things. I understand the rationale for a company to use non-native platforms. And can appreciate the tech behind it. But this article is about getting featured by Apple and creating stand out UX.
For the former non-native is just a no-no and for the latter, non-native does not create the same UX experience. It just doesn't.
Fair enough on the featuring.
On the UX side, do you think there are categories of apps that are better suited for native? Some of the apps on this list seem to have some pretty solid, even in some cases unique (Gyroscope), UX: https://www.purrweb.com/blog/best-react-native-apps/
I do, I think there are many cases where non-native works equally as well. I also think it's an argument based on Locale as well as app type. For instance, if you are launching service app in Asia then it makes sense to build non-native as there is a bigger divide with market share between iOS and Android devices. On the other side of the coin, if you are launching a utility app in US, I think there is a less of a need to build non-native as iOS is the more dominant platform by far and you can get away with only building for iOS at least to begin with.
At the end of the day, I am biased as an iOS developer. But just in-terms of the tech, unfortunately non-native platforms can never run quite as well as a native language app.
Thanks for sharing Gyroscope, I have that app and did not realise it was non-native. That is a nice surprise. And also, thanks for the healthy discussion!
When I worked at Xobni, Apple featured our app SmartrContacts and it was like turning on a firehose. Great advice and I'm hoping for lightening to strike twice for me as well.
I know, it’s a game changer, isn’t it? Good luck on the next one dude!
Nice post Joe
Good luck with that ADA 🙂
🍻
Cheers Shaun. One can dream 😂
Well done! 👏
As an Android user, and having published only one app 10 years ago, I didn't realize Apple could be so picky about data collection.
Great one! And completely agree with “Native Only” part 👍
Thanks my dude. I appreciate the support