mirror of
https://github.com/Such-Software/hash-wallet.git
synced 2026-10-17 05:41:29 +02:00
Avoids any confusion / potential trademark friction with HashWallet
(Spanish hardware-wallet company). Hash Bags is a more distinctive
name, harder to collide with, and we can still rank for 'hash wallet'
search via App Store / Play Store subtitle ('Hash Bags - A Wallet
for your Coins').
What changed (all user-visible strings):
- Launcher labels: android/app.properties, scripts/android/app_env.sh,
scripts/ios/app_env.sh, linux window title (CMakeLists +
my_application.cc)
- In-app text: lib/generated/i18n.dart + ARB sources under res/values/
- Brand docs: README.md, CONTRIBUTING.md, PRIVACY.md,
assets/text/Terms_of_Use.txt, assets/text/Release_Notes.txt
- hash.boats website: index.html, og-image.svg + regen og-image.png,
site.webmanifest, styles.css comment, splash/confirm/pulse/mark/
lockup svg titles, report/index.html, server/server.js
- CI workflow display names ("Hash Bags Linux build", etc.)
What did NOT change (deliberate):
- Bundle ID / Package: com.suchsoftware.hashwallet (immutable app
identity on App Store + Play Store — changing == orphaning the app)
- Binary name: hash_wallet (Linux executable)
- Dart import paths: package:hash_wallet/...
- Git repo: hash-wallet (Such-Software/hash-wallet)
- URL scheme: hashwallet:// (internal deep links)
- support@such.software (no domain change yet)
- App Store / Play Store listing names (whatever was registered there
stays; we updated launcher label only)
- hash.boats domain (still the wallet site)
Also kept the '#ash Wallet' wordplay in the nav but updated to
'#ash Bags' so the # mark still serves as the H. Nav reads:
[# mark] #ash Bags
Website hero tagline now matches the App Store sub-title concept:
'A wallet for your coins. Open-source, non-custodial, multi-chain.
Privacy-leaning by default.'
108 files modified, ~674 string replacements.
Material 3 Theming System
This directory contains the Material 3 (M3) theming implementation for Cake Wallet. The theming system is now fully based on Material 3 color tokens and patterns, with all custom theme extensions removed for simplicity, maintainability, and compliance with Material Design 3 guidelines.
Directory Structure
lib/themes/
├── core/ # Theme state management and base theme logic
├── theme_classes/ # Light and dark theme data definitions
├── extensions/ # (Optional) Theme extensions for specific widgets/pages
├── utils/ # Utilities for theme management
└── README.md # This file
Key Features
- Material 3 color system with semantic color tokens
- Dynamic color support (when available)
- MobX-based state management
- Simplified theme management
- Consistent design language across the app
Usage
Accessing Theme Colors
final colorScheme = Theme.of(context).colorScheme;
final primaryColor = colorScheme.primary;
final onSurfaceVariant = colorScheme.onSurfaceVariant;
Available Color Tokens
Material 3 provides a comprehensive set of semantic color tokens that adapt to light/dark themes:
primary/onPrimarysecondary/onSecondarytertiary/onTertiaryerror/onErrorbackground/onBackgroundsurface/onSurfacesurfaceVariant/onSurfaceVariantoutline,outlineVariant- ...and more (see Flutter's ColorScheme)
Theme Management
Theme mode state (light/dark/system) and switching is handled via MobX stores in core/. Use the provided store to get/set the current theme mode and listen for changes.
// Example: Getting the current theme mode
final themeStore = ... // Obtain from provider or context
final isDark = themeStore.isDark;
// Example: Switching theme mode
await themeStore.setThemeMode(ThemeMode.dark);
Best Practices
- Always use semantic color tokens from
ColorSchemeinstead of hardcoded colors. - Leverage Material 3 components wherever possible for consistency and accessibility.
- Use the MobX theme store for all theme-related state and switching.
- Test in both light and dark modes to ensure good contrast and appearance.
- Keep any theme extensions minimal and focused (if used at all).
- Do not reintroduce custom theme extensions unless absolutely necessary and not covered by Material 3.
Adding or Modifying Themes
- To update theme colors, edit the files in
theme_classes/(e.g.,light_theme.dart,dark_theme.dart). - To add a new theme variant, create a new file in
theme_classes/and update the MobX store incore/to support it. - For widget-specific theming, prefer using Material 3's built-in tokens. Only use a theme extension if there is no Material 3 equivalent.
Contributing
- Follow Material 3 color system and accessibility guidelines.
- Ensure proper contrast ratios for accessibility.
- Test all changes in both light and dark modes.
- Update this documentation if you add new color tokens or theme variants.
- Keep theme files organized and focused.