Article5 min readUpdated
Settings Screen Design: Profile, Logout and Delete Account
Settings screen design for Indian apps: profile screen UI, account settings order, safe logout, delete account steps, language setting and sample wording.
A customer in Bardhaman installs your app, orders twice, then wants to change the phone number, switch the app to Bengali and stop the promotional messages. She opens the profile tab and cannot find any of it. Settings screen design is the work of putting these controls where a person expects them, in plain words. The settings screen is the place where a user manages their account, preferences and safety options, and the profile screen is the page that shows who they are in the app.
What should a profile screen show?
The profile screen should show the person first and the shortcuts second. It is a hub, not a form.
From top to bottom, the profile screen UI usually has these parts.
- Photo or initials, name, and mobile number. With an "Edit" link. Example: "Riya Sen, +91 98765 43210".
- A status line, if useful. "Verified" or "Member since 2025", only if it is true.
- Activity shortcuts. "My orders", "Saved addresses", "Wishlist", "Payment methods".
- Help and info. "Help and support", "About", "Terms and Privacy".
- Settings. One row, or a gear icon at the top right.
- Logout. Last, in plain text.
Let users change the photo and name without any ceremony. Do not ask a new user to fill the whole profile. Show a small prompt: "Add your email to get invoices", and let them skip it. For the wider rules on forms, see form design best practices.
How should account settings be organised?
Account settings should be grouped under short headings, with the most used group first. Long flat lists make people scroll and give up.
| Group | What goes inside |
|---|---|
| Account | Name, mobile number, email, change number |
| Preferences | Language, theme, notifications |
| Privacy and security | Login devices, permissions, download my data |
| Payments | Saved UPI IDs, cards, refunds |
| Help | Support, FAQs, report a problem |
| Account actions | Logout, delete account |
Keep each row to a single line where possible, and keep the row height large enough for a thumb, about 48 pixels or more. Dense rows cause wrong taps on small phones. Each row has a label on the left, the current value on the right in grey, and an arrow. Example: "Language English". Users see the current choice without opening the row.
Use switches for settings that change at once, such as "Order updates". Use a new screen for choices that need a list, such as language. Write labels as nouns or short verbs, not as questions. "Notifications" is better than "Do you want notifications?". For what each notification type should do, see notification UX for push, SMS and WhatsApp.
Where does the language setting belong?
The language setting belongs in two places: on the first screen, and in settings near the top. Many users in tier-2 and tier-3 cities read comfortably in Hindi, Bengali, Tamil or another language rather than English.
- Show each language in its own script: "हिन्दी", "বাংলা", "English". Do not write "Hindi" in English letters only, because some users will not read it.
- Show the current choice in the row: "Language বাংলা".
- Apply the change at once, without restarting the app.
- Do not translate the language names into the current language. A user who picked the wrong language by mistake must still be able to find the right one, so the list should look the same in every language.
A language list with a radio button beside each name is enough. Test with real text, because Bengali and Hindi letters need more height. For more on this, see regional language app design in India.
How do you design logout and delete account safely?
Logout needs one confirmation. Delete account needs a longer path, because it cannot be undone. Keep both at the bottom of the settings screen, away from daily options.
Logout
Tapping "Logout" opens a small dialog.
- Title: "Log out of your account?"
- Body: "You will need your mobile number and OTP to log in again."
- Buttons: "Cancel" and "Log out".
Place "Cancel" as the safer, more visible choice. After logout, return to the login screen. See login and OTP screen design for that flow.
Delete account
This is a short flow with four steps.
- Row label: "Delete account" in red text, no icon.
- Explanation screen: "This will remove your profile, saved addresses and order history. Orders in progress must finish first. This cannot be undone."
- Optional reason list: "I do not use the app", "I have another account", "Privacy concerns", "Other". Make it skippable.
- Final confirmation: type the last 4 digits of the mobile number, or enter an OTP, then tap "Delete my account".
After deletion, show: "Your account has been deleted. We are sorry to see you go." Some apps keep a short grace period, such as "You can recover your account within 14 days". Only write that if your team has decided it. This is a product and legal decision, so I design the screens and your team confirms the rules.
What states and errors does the settings screen need?
Every settings change has a loading, success and failure state. People trust a switch only when it confirms.
- Saving: a small spinner on the row, or "Saving...".
- Saved: a brief message at the bottom, "Changes saved".
- Failed: the switch returns to its old position, with "Could not save. Check your connection and try again."
- Edit phone number: send an OTP to the new number before changing it. Message: "We sent a code to +91 98765 43210 to confirm this number."
- No profile photo: show initials in a coloured circle, not a grey person icon.
- Offline: let people read settings, and disable only the changes that need the network.
See empty, loading and error screens for the general states.
Which settings screen mistakes happen most?
Most mistakes come from treating settings as a dump for everything the team could not place elsewhere.
- Putting Logout in the middle of the list, next to daily options.
- Hiding the delete account row so well that users email support instead.
- Using technical words such as "Push", "Cache" or "Sync".
- Showing a switch with no label for its on or off state.
- Making users scroll through 25 rows with no headings.
- Putting important help below a long list of legal links.
- Forgetting large text and accessibility. See accessibility in app and web design.
If you want your profile and settings flows designed with clear wording and tested states, see my mobile app design service.
Frequently asked questions
Where should the settings screen be in an app?
+
Usually under a Profile or Account tab, or behind a gear icon at the top of the profile screen. Users look for it there first.
Should logout ask for confirmation?
+
Yes, one short confirmation is enough. Logging out by accident is annoying when the user must log in again with an OTP.
Is a delete account option required?
+
App stores expect apps that let people create an account to also let them start deleting it from inside the app. Check the current store rules with your developer.
Should the language setting be in settings only?
+
No. Offer it at the first screen too, and keep it in settings so users can change their mind later.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.