feat(nav): move profile to top-right avatar, 3-tab native nav#291
Merged
Conversation
Simplify native navigation from 4 tabs to 3 (Home / Explore / Feed) by removing Profile from the bottom tab bar and surfacing it as a consistent avatar button in the top-right of every tab header. - TabHeader: new `showProfile` prop (default true) renders the user avatar as a `/profile` entry point. Native-only — web keeps its existing WebHeader / WebBottomNav profile entry untouched. - (tabs)/_layout: profile screen set to `href: null` so /profile stays routable (web's WebBottomNav + SettingsPanel still link to it) while dropping the native tab icon. Avatar is hidden on the profile screen's own header. No web routing changes, to stay clear of the in-flight web-nav redesign. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying chinmaya-janata with
|
| Latest commit: |
91130c9
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://271bd306.project-janatha.pages.dev |
| Branch Preview URL: | https://feat-v2-tab-nav-profile-head.project-janatha.pages.dev |
This was referenced May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Simplifies native navigation from 4 tabs to 3 (Home / Explore / Feed) by moving Profile out of the bottom tab bar into a consistent avatar button in the top-right of every tab header.
Motivation: simplify navigation (and the home screen) ahead of the MSC launch — the demo feedback was that the app felt busy. The web build already does this (avatar in
WebHeader); this brings native in line.Changes
TabHeader.tsx— newshowProfileprop (defaulttrue) renders the user's avatar as a/profileentry point, shown on Home, Explore and Feed. Native-only (Platform.OS !== 'web'); on the profile screen itself it's passedfalse.(tabs)/_layout.tsx— profileTabs.Screenset tohref: null: removes the native tab icon while keeping/profilemounted and routable. Removed the now-deadAvatartab-icon + import.Deliberately scoped to avoid colliding with other in-flight work
(tabs), so on web it still renders withinWebHeader/WebBottomNav— pixel-identical. This keeps the PR clear of the in-flight web-nav redesign branch (redesign-web-nav-and-desktop). The only shared file is(tabs)/_layout.tsx; the overlap is one line (the Explore header), a trivial merge./profileroute preserved —WebBottomNavandSettingsPanellinks keep working.v2for independent mergeability (no dependency on draft PRs).Verification
tsc --noEmiton the frontend: 0 errors in the changed files (8 pre-existing baseline errors elsewhere, unrelated).npm install). Recommend a quick simulator pass to confirm: 3 tabs render, avatar appears top-right on all three, tapping it opens/profile, and the profile screen's own header shows "You" + settings with no avatar.UX note
Profile opens as a tab-style screen (no back-arrow) — consistent with its current behavior (you return via the tabs). If we'd prefer a pushed screen with a back arrow, that's a follow-up (it touches root-stack routing + web chrome, so I kept it out of this PR).
🤖 Generated with Claude Code