Your onboarding is not too long. It is in the wrong order.
Users do not abandon onboarding because there are 7 screens. They abandon it because the product asks for effort before it has shown why the effort matters.
Teams often treat onboarding as a length problem. Remove 2 questions, hide 1 screen, call it friction reduction. Sometimes that works. More often, the problem is sequence.
Show the product before asking for work
Do not ask for permissions, preferences and profile details before a person understands what they will receive. Give them a useful glimpse of the product, then ask for the information that makes the next step better.
Ask at the moment of need
Location makes sense when someone searches nearby. Notifications make sense when a user has something worth being notified about. A profile photograph makes sense when they are about to participate socially. Earlier is not always better.
Every onboarding question should have a visible job.
Let people change their mind
Good onboarding gives users a way past uncertainty: skip for now, edit later, correct a mistake and understand what will happen next. The goal is not to collect every field. It is to help somebody reach their first useful moment.
Test the first 10 minutes
Watch new users set up the product without coaching. Where do they hesitate? What do they assume? What information do they look for before agreeing to continue? Fix the order, then decide whether the flow is still too long.
