AlphaBack had a very productive week 💪 Notably, we released our new feature (leaderboard upvoting), reconfigured our CMS, and hit our launch preparation goals. We also got valuable feedback from three naysayers.
- New feature released. Our leaderboard is in the wild as part of release v0.0.4 in the Chrome Web Store. Here’s a quick walkthrough of what’s new, including onboarding flow, an NFT gallery, upvoting with MATIC, and the uninstall exit survey.
- Pipeline.We have more than 10 projects ready to launch on Sept. 22 for the first upvote competition 🙌 Beyond that, we have a total of 31 projects in the pipeline.
- Content Machinery. We released our website and blog content on a single server using WPEngine. This enhancement will make it simpler to create webpages given that the footer, header, and other elements are templated (savings us time and reducing potential for errors). Additionally, our blog CMS is now accessible online so that teammates can post content, too.
- Project Feedback. Out of 33 projects that we’ve spoken to in the past two weeks, three have said that they do not feel comfortable pushing their community to download an extension. Their reasoning was similar: they believe their community is too security-conscious to install a browser extension.
- One project eventually overcame this objection after learning that the extension is published and auditable by anyone.
- Another project said that they would participate if the value proposition was stronger (e.g., 5,000 users isn’t worth the risk, but they would proceed if they were getting attention from 100,000 users).
- The third project – which focuses on cyber security – could not imagine circumstances under which they encourage users to install a browser extension as part of a co-promotion.
- Do you know an SEO expert? I’d love to get their feedback on our CMS setup.
As usual, thank you for your ongoing support 🙏