Design Principles
The rules that guide every product decision at Sippy.
Simplicity first
If your grandmother cannot use it, it is not done. Every feature, every flow, every message goes through this filter. Sippy should feel obvious the first time you use it. No tutorials, no onboarding tours, no "learn more" links that lead to documentation. The product teaches itself through use.
When in doubt, we remove. Fewer options, fewer screens, fewer words. Complexity is the enemy of adoption -- especially for people who have never used a digital financial tool before.
Non-custodial by default
Your money is yours. Sippy never holds, controls, or has access to your funds. Your wallet is created for you, secured by Coinbase's embedded wallet infrastructure, and only you can authorize transactions.
This is not a philosophical stance -- it is a safety decision. If Sippy were hacked tomorrow, no user funds would be at risk because we do not hold user funds. There is no pool of money to steal, no database of private keys to leak. The safest way to protect people's money is to never touch it.
Invisible complexity
Blockchain should be invisible to the user. Sippy does not mention gas fees, transaction hashes, network selection, or token approvals in normal use. All of that exists -- and it is important -- but it happens behind the curtain.
When you send a message, you do not think about TCP/IP. When you send money through Sippy, you should not think about Arbitrum. The technical layer exists to serve the user, not to impress them.
LATAM-native
Sippy is built for Latin America from day one. Not adapted from a US product, not translated from English, not shoe-horned into the region as an afterthought.
That means:
- WhatsApp-first because that is what people actually use
- Spanish, Portuguese, and English because the region speaks all three
- On-ramp partners that accept local currencies because dollars are only useful if you can get them
- Low-bandwidth friendly because not everyone has fast, unlimited data
- Dialect-aware because a Colombian and an Argentine speak the same language differently
Trust through transparency
Every transaction is verifiable on-chain. Your balance, your history, your wallet address -- all of it can be independently checked on a public blockchain explorer. Sippy does not ask you to trust a dashboard. The data is on-chain, and anyone can verify it.
Transparency is not a feature we ship once. It is an ongoing commitment to making every part of the system auditable, explainable, and honest.