Edit Profile

Edit profile fields and avatar with save.

Preview

Open the exact pattern in the real BeeUI Web Showcase. This is a Web runtime preview, not native-device evidence.

Each named state is directly addressable:

The same source is available at apps/showcase/patterns/account-settings/screens/edit-profile-screen.tsx.

Composition

Principal public BeeUI exports used by this screen: AlertBanner, Avatar, Box, Button, Field, HStack, Input, Textarea, VStack.

The pattern is a composition recipe rather than a new framework layer. Follow the linked component contracts for state, provider, platform and accessibility details.

State and callback contract

The screen is controlled through EditProfileScreenProps. User intent crosses the application boundary through onBioChange, onChangeAvatar, onDisplayNameChange, onEmailChange, onSave, onUsernameChange; fetching, routing, persistence and side effects remain application-owned.

// from apps/showcase/patterns/account-settings/screens/edit-profile-screen.tsx
export type EditProfileFieldErrors = Partial<
  Record<'displayName' | 'username' | 'bio' | 'email', string>
>;

export type EditProfileScreenProps = {
  bio: string;
  displayName: string;
  email: string;
  error?: string;
  fieldErrors?: EditProfileFieldErrors;
  imageUri?: string;
  onBioChange: (value: string) => void;
  onChangeAvatar: () => void;
  onDisplayNameChange: (value: string) => void;
  onEmailChange: (value: string) => void;
  onSave: () => void;
  onUsernameChange: (value: string) => void;
  saving?: boolean;
  username: string;
};

Common product states such as loading, success, empty, error, permission-like recovery, filtering/search/selection or pagination are represented only where the actual screen source exposes them. The pattern docs do not invent backend states that the fixture does not render.

Responsive contract

Read from the screen file and the 1 pattern-local file in its runtime import closure, direct and transitive: account-settings/screens/edit-profile-screen.tsx, account-settings/components/settings-screen-shell.tsx. Every fact below is scoped to those files and to nothing else.

BeeUI layout primitives rendered: Box (account-settings/components/settings-screen-shell.tsx, account-settings/screens/edit-profile-screen.tsx), HStack (account-settings/screens/edit-profile-screen.tsx), KeyboardAwareScreen (account-settings/components/settings-screen-shell.tsx, the branch taken when keyboardAware is true), VStack (account-settings/components/settings-screen-shell.tsx, account-settings/screens/edit-profile-screen.tsx).
Scroll ownership: no ScrollView, FlatList, SectionList or VirtualizedList element in account-settings/screens/edit-profile-screen.tsx; account-settings/components/settings-screen-shell.tsx, the branch taken when keyboardAware is true; scrolling is owned by the composed KeyboardAwareScreen, whose own page derives it.
Horizontal scrolling: no horizontal scroll container in account-settings/screens/edit-profile-screen.tsx, account-settings/components/settings-screen-shell.tsx.
Width constraint: contentWidth="md" (account-settings/components/settings-screen-shell.tsx, the branch taken when keyboardAware is true).
Breakpoint-prefixed utility classes: none in account-settings/screens/edit-profile-screen.tsx, account-settings/components/settings-screen-shell.tsx.
Platform-prefixed utility classes: web:py-10 (account-settings/components/settings-screen-shell.tsx).
Platform branching: no Platform.OS or Platform.select call in account-settings/screens/edit-profile-screen.tsx, account-settings/components/settings-screen-shell.tsx.
Viewport measurement: no useWindowDimensions, Dimensions.get or breakpoint hook in account-settings/screens/edit-profile-screen.tsx, account-settings/components/settings-screen-shell.tsx.

BeeUI’s mobile-first responsive contract is the framework-level document; the list above states only what this screen’s own files declare, and says nothing about how the composed components behave internally.

Accessibility

Roles this screen sets itself: none set in account-settings/screens/edit-profile-screen.tsx, account-settings/components/settings-screen-shell.tsx.
Accessibility states and properties it sets itself: none set in account-settings/screens/edit-profile-screen.tsx, account-settings/components/settings-screen-shell.tsx.
Semantics inherited from composed BeeUI families: AlertBanner (account-settings/screens/edit-profile-screen.tsx, only when error is true), Avatar, Box, Button, Field, HStack, Input, KeyboardAwareScreen (account-settings/components/settings-screen-shell.tsx, the branch taken when keyboardAware is true), Text, Textarea, VStack — each family’s own page derives the roles and states it sets; they are not restated here.

Touch-target size, focus order, announcements, RTL, large-text and reduced-motion behavior are not derived from this source — see the Accessibility guide for what is and is not covered by evidence. A Web preview does not substitute for VoiceOver/TalkBack runtime evidence.

Application ownership boundary

Intentionally excluded: Avatar upload, validation, and profile persistence.

BeeUI does not take ownership of app routing, authentication/business rules, APIs/data fetching, persistence, form/state frameworks, chart frameworks or backend logic merely because a pattern visually composes those product concepts.

Source ownership

EditProfileScreen is Showcase source you copy, not a package export: it is not shipped from any @beemvp/beeui-* package, and the Registry CLI (pnpm beeui list / pnpm beeui add) does not carry pattern screens. Copy apps/showcase/patterns/account-settings/screens/edit-profile-screen.tsx into your app and adapt it directly. Only the individual BeeUI components it composes (linked above) are available for source ownership through the repository-local Registry workflow; see CLI & source ownership for both the published npx @beemvp/beeui-cli@next path and the repository-local checkout path.