
We use Matrix as the foundation for secure, decentralized communication inside the Walme ecosystem.
Matrix allows us to build messaging that is end-to-end encrypted, censorship-resistant, and not dependent on a single centralized provider. This aligns directly with our core principles around self-custody, user control, and privacy.
By using an open protocol, we ensure transparency, long-term flexibility, and the ability to evolve communication features as a native part of our Web3 wallet hub — without locking users into closed systems.
Alternatives Considered
Report
1 view
We chose Kotlin as the core language for our Android app because reliability, performance, and long-term maintainability are critical for a crypto wallet.
Kotlin’s strong type safety and modern language features help us reduce errors in security-sensitive code, while its excellent Android ecosystem support allows us to build fast, responsive, and stable user experiences. This gives us confidence to ship features like multi-wallet management and in-app swaps without compromising quality or security.
Alternatives Considered
Report
1 view
We chose Unstoppable Domains to make crypto interactions more human-friendly and easier to use.
Instead of long and error-prone wallet addresses, Unstoppable Domains allow users to send and receive crypto using simple, readable names. This significantly reduces friction and the risk of mistakes, which is critical for everyday crypto usage.
Using blockchain-based domains also aligns with our focus on user ownership, decentralization, and portability across the Web3 ecosystem.
Alternatives Considered
Report
1 view
We use GitHub as the backbone of our development workflow to ensure transparency, code quality, and smooth collaboration across the team.
GitHub allows us to manage version control, reviews, and releases in a structured way, which is especially important for a security-sensitive product like a crypto wallet. Pull requests, code reviews, and automated checks help us catch issues early and maintain a high standard as the product evolves.
Alternatives Considered
Report
1 view
We chose Figma because collaboration speed and clarity were critical for building a complex Web3 product. Real-time collaboration between designers, product managers, and developers allowed us to iterate fast, align on UX decisions, and reduce handoff friction.
Figma’s component system, shared libraries, and prototyping tools helped us keep a consistent design language while moving quickly from concepts to production-ready screens — especially important when designing a multi-wallet hub with complex user flows.
Alternatives Considered
Report
2 views




