Align App Store, Play Store and Chrome Web Store listings around a unified Bread Wallet experience

## Summary

The Bread Wallet listings on the iOS App Store, Play Store, and Chrome Web Store are not consistent with each other.

They use different descriptions, feature emphasis, screenshots, and visual presentation. This can make the mobile and browser versions feel like independently marketed products instead of different platform versions of the same wallet.

Users may install Bread on multiple devices, so the listings should reinforce the same core product identity, value proposition, security model, and terminology across platforms.

## Environment

- Product: Bread Wallet by Miden
- Platforms:
- iOS App Store
- Chrome Web Store
- Feedback date: 2026-08-04
- Devices used during testing:
- iPhone 17 Pro
- MacBook with Apple M2 Pro

## Steps to observe

1. Open the Bread Wallet listing in the iOS App Store.
2. Review the product description, feature claims, screenshots, branding, and terminology.
3. Open the Bread Wallet listing in the Chrome Web Store.
4. Compare the description, feature claims, screenshots, branding, and terminology between the two listings.

## Actual result

The listings communicate noticeably different product experiences:

- The App Store description focuses mainly on:
- Privacy by default
- Self-custody
- Key ownership
- Device-based security
- Simple sending and receiving

- The Chrome Web Store description focuses mainly on:
- Browser-wallet capabilities
- Optimization for Miden
- Security and performance claims
- Support for different transaction types

- The screenshots use different visual styles and highlight different features.
- The feature order and core messaging are not aligned.
- Users may not immediately recognize that both listings represent the same wallet and security model.

Platform-specific capabilities are expected, but they should supplement a shared core message rather than create two separate product identities.

Inconsistent listings may:

- Reduce trust when users move between mobile and browser versions.
- Make users question whether both applications are official.
- Create different expectations about privacy, security, and supported functionality.
- Make cross-device onboarding feel fragmented.
- Increase the risk of users installing an unofficial or incorrect product because the official listings do not look sufficiently connected.

For a wallet, recognizable and consistent branding is also part of the security experience. Users should be able to confidently identify the official product on every supported platform.