Launcher onboarding and default home setup
Evie Launcher opens with an onboarding screen explaining that it needs storage, location, and contacts access for wallpaper effects, nearby information, and quick contact actions. It also prompts users to set Evie as the default launcher for a simpler, faster home screen.
Changing the default home app affects the main phone experience, so users should understand how to switch back before continuing. A launcher should feel comfortable for daily navigation, search, widgets, and app access.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
Location, contacts, and home personalization
The visible prompts include location access and contacts access, while Android settings show files and media, music and audio, nearby devices, photos and videos, microphone, phone, and additional permissions. These can support launcher search, recommendations, shortcuts, wallpaper behavior, and contact actions.
Users should grant only the permissions they actually want the launcher to use. Contacts and location can expose personal context, so privacy-sensitive users may prefer a minimal setup.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
System settings and launcher control
Evie includes permissions for launcher settings, wallpaper changes, status bar expansion, account access, phone actions, and system setting changes. These capabilities can make a launcher feel integrated, but they also give it influence over core phone behavior.
Review default home selection carefully and keep another launcher available if needed. If Evie does not behave as expected, Android settings can be used to change the default home app back.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
