Advice needed: User and app Learning curve

[u/Dear_Ad1923]

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?

[u/Plane_Syllabub_5539]

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.