Team: Gabriel, Vaclav, Pedro
Over our virtual offsite session, our team reviewed the current state of Waku web app development, the assumptions we’re building on, and the direction we want to take.
We agreed that our main working assumptions are:
-
Waku network is functional and stable.
-
Messaging API is defined and usable.
-
Users and developers value privacy and censorship resistance.
Key discussion points
We looked at the unique value Waku can bring to web apps, such as offering a browser-native, P2P alternative to centralized backends. We talked about common architectural patterns emerging from our work, the need for better persistent storage via Codex, and how to identify the right target audiences: from Logos community members to hackathon builders.
Challenges came up around UX, shifting from centralized to P2P architecture, ensuring product-market fit, and maintaining apps over time. We also stressed the importance of keeping code open, making it easy for others to contribute, and setting a standard “deliverables” list for any app we release.
Recommendations moving forward
-
Keep building apps: new ideas, Web2 clones, Web3 improvements, and niche use cases (activism, whistleblowers).
-
Derive and document architectural patterns, especially for identity, state sync, and decentralized persistence.
-
Integrate persistent storage with Codex for complete use cases like large file transfer and history.
-
Maintain existing apps (Quaku, Opchan, WhisperBox, Trollbox) and keep them aligned with Waku updates.
-
Define standard deliverables: accessible deployment, public repo, spec, forum post, demo video, social posts, and inclusion in the Awesome Waku Repo.
-
Encourage external contributions with “good first issues” and clear entry points.
-
Prioritize based on recurring patterns before creating libraries or abstractions.
-
Do outreach and surveys with communities (Logos, Privacy Now, Railgun, etc.) to identify real needs.
-
Use content formats like live coding streams to show integrations and attract developers.
This direction should help us grow a stronger ecosystem around Waku, make it easier for newcomers to contribute, and keep our apps relevant and maintained.