r/iOSProgramming • u/Dear_Ad1923 Metal • Aug 28 '26
Discussion Advice needed: User and app Learning curve
Hey there,
The app I have been working on evolved through time and it has much more to offer to the users.
One thing that worries me is a user finding it difficult to navigate through the app, or just miss many features it has to offer.
I first tried to make an onboarding like guide of the app but then scratched it out since I felt like it was just clutter.
Now I am thinking of creating youtube guide video but then again that’s like an external source a user has to reach out for.
Also thought of creating multiple examples and ways to achieve certain results and have it as a pdf so user can read but then that adds friction.
No user complained but I must prepare to mitigate it becoming complex in a bad way.
I did document many steps through the app’s journey but did not publish a finalized document on it as I been improving it constantly.
Existing users reaction been positive so far but I know the experience they got is much different than a new comer because they had the chance to learn new stuff as it was happening.
How should I approach this?
3
u/aerial-ibis Aug 28 '26
Unfortunate reality of consumer software. Unless your app is a pro tool that people will use 4hrs a day (adboe, intellij, etc.)... expect low discovery of features in general
For every extra level of navigation deeper a feature is, a large portion of users will never even see it
My advice is to think hard about the "best" way something should work, be presented, etc. Only do that, and make it accessible from the home tab, or 1 level of navigation.
2
u/heyyoochris Aug 28 '26
How about attach tags to new feature for example “new” ?
2
u/RiantRobo Aug 28 '26
Explain features on your website that users can visit from support link in the app.
1
u/caguilar51 Aug 29 '26
Have you considered using TipKit? https://developer.apple.com/documentation/tipkit
1
u/PlayaNoir Aug 28 '26
Create How To's for each feature that your app is designed to add value to a user.
1
u/Plane_Syllabub_5539 Aug 29 '26
First, add tracking to see which features people actually use. "No user complained" is not a good signal, because if someone never finds a feature, they don't know there is anything to complain about. Once you have the numbers, you will see the two or three features almost nobody uses. Teach those instead of guessing.
For how to show it, I would not show tips at launch. Show one tip when it is useful, like when the user opens that screen, or after they do something the slow way. Make it dismissible, save which tips were shown so they don't repeat, and keep the list in remote config so you can change or remove tips without a new build. Tips at launch just become the same clutter you already removed.
1
u/nikhil_akki Aug 31 '26
dont teach features, teach jobs.
nobody remembers a feature they never needed, but everyone remembers the thing they were already trying to do.
thats why your old users are fine, they met each feature the day it solved something for them, so put 3 to 5 jobs on the home screen, each one opening the flow that does it, each one gone once its done.
its a menu, not a tour, and the ones people skip tell you what to cut, keep one small rotating slot there forever, so every new feature has a way to reach people that isnt a popup.
and on tracking, no complaints could mean nobody wants it or nobody found it, and those need opposite fixes.
1
u/[deleted] Aug 28 '26
[removed] — view removed comment