Turning Peel into a dApp laboratory that publishes highly focused, tightly-scoped, and value-based front-ends (dApps) built atop of the Juicebox protocol.
Peel Renewal Proposal [September ‘23]
Peel Renewal Proposal [December ‘23]
Over the course of the last 6-12 months, Peel (and other contributors) have made immense efforts to both steer the product toward a level of PMF and optimize the user experience to capitalize on growth opportunities. We have done this by attempting to cater to an incredibly flexible, feature-dense protocol, whilst simultaneously positioning the messaging and product toward a crowdfunding-style platform, in line with user demand. We have created a “super app” that pleases everyone and no one at the same time, and thus efforts have fallen flat with traction while the industry continues to produce growing products amid a bear market.
Whilst there are many reasons why the product has fallen flat with growth efforts, it mostly boils down to complexity, foundations, and conflicting goals. For a full breakdown and analysis of the observed issues and foundations, see Juicebox Observations & Analysis.
Recently, Juicebox has been exposed to an opportunity to partner with hackathon providers and platforms to help solve a gap where builders are looking to get funding to take their projects to the next level. As ETH New York inches closer, we evaluated what it would mean to have hundreds of projects published on Juicebox in search of funding, to realize that their project would not meet their expectations due to the foundations of the platform. See Token-based funding mechanism, Fulfillment-based funding mechanism and Donation-based funding mechanism for further information.
To properly capitalize on this go-to-market opportunity, we must get the foundations right, or work in collaboration with ETHGlobal to get it tight. For more information on the go-to-market, see ‣ for further information.
As outlined in the structure below, we’re exploring restructuring the ‘product’ and re-deploying as tightly-focused dApps that serve the specific use cases, with a top-level website driving education and entry to the protocol.
Such change would turn Peel into a ‘dApps Lab’ of sorts, where we publish dApps that better suit user goals. The first several apps would act as inspiration to encourage other developers to build and publish their own dApps, whilst catering to the specific use cases of existing Juicebox users through focused interfaces.