As part of the Waku 2025H2 roadmap, we propose (yet to be approved) to build 10 Waku Web Apps and 1 Logos Core app.
The objective is “Teach them how to hunt”, by demonstrating what and how you can build with Waku. Hence, the main focus is to build functional apps, with clean code around Waku usage.
The roadmap/commitment is not prescriptive on what apps.
I see 3 types of apps we can build:
- Internal tools: This is Qaku, Forum, Whisperbox (forms) - apps that we can dogfood and use internally. I think it’s a good start because we will have (limited) users for those apps, but users nonetheless. The internal dogfooding and customers force us to build reliable apps, and ensure the underlying infra and libraries are working.
It is also a good opportunity to build foundations, such as a forum library, that can open the door to other type of apps (eg reddit like, 4chan like, etc)
The caveat for those apps is that they are often web2 clones. Which means:
- Do not fully leverage Waku’s added values of privacy and censorship-resistance
- May have existing Web2 revenue models, which may not easily convert to a tokenomy/web3 revenue model.
Hence, while useful, I expect those apps to have limited growth opportunity beyond IFT CCs or Logos movement.
-
Useful Dapps: Aka apps that really solve a problem and need to be private and censorship resistant, with a true potential to be useful. These are the apps I expect to be built for Logos. Jarrad has a list on the Logos wiki of type of apps we are talking about (can’t find the link, will edit if I do).
Contrary to (1), there may not be an evident design to copy from the web2 world. For those apps, we need users to help drive the design process. This is the kind of apps that need to come from talking with potential users that are getting in the Logos movement, or that we meet at conference, meetups, cells etc. WhisperBox (forms) do fit in this category as a DAO was interested in it.
I definitely want all of us to keep our eyes and ears opens for those, and build what we hear would be useful to people. This present forum is another place to gather ideas and requirements. -
Toys and experiments: I see a third category where we may not have clear internal or external users, but we experiment with a technology unrestricted by central servers and admins. I see Kurate falling in this domain. Where we can do social experiments and just play with concept and technology. Most of it may not be useful, but learning and libraries we extract could then become useful for (1) and (2).,
Kurate is definitely a great example for this one (playing with the concept of abstract personas where post under their feed are written by anyone, and curated by a community an anonymous manner thanks to zk tech).
If any of the apps we build sticks and we actually get interest, then we can propose to invest more to those apps as part of 2026H1 roadmap. Including aiming for market-fit, developing business model, etc.
In the mean time, I encourage everyone to:
- amplify what they hear from the community around (2),
- highlight what internal tools we could replace (1),
- play with Waku and build (3)
- post any type of ideas they want to see build, The Waku app/chat engineers will appreciate a pool of idea to choose from.