Dear Proposer,

Thank you for your proposal. Our first vote on this proposal is AYE.

The Big Tipper track requires 35% participation and simple majority of non-abstain voters according to our voting policy. This proposal has received five aye and one nay votes from ten members, with one member abstaining. Below is a summary of our members' comments:

> In the referendum, opinions varied among voters regarding the proposal's value and its potential impact on the ecosystem. Some expressed skepticism, noting the existence of similar projects and questioning the necessity of the proposal. Others supported it, acknowledging the reasonable request for funding considering the effort involved. A few voters were curious about future developments, while one chose to abstain due to a conflict of interest. Overall, the responses reflected a mix of cautious support and reservations about the project's significance.

The full discussion can be found in our internal voting.

Kind regards,
Permanence DAO

Lucky Friday have voted AYE. Please consider this a temporary notification after our preliminary vote has gone on chain. If you would like additional feedback on our rationale for this vote, please join our OpenGov Public Forum on Telegram here: https://t.me/+559tyPSfmGg0NzUx

Lucky Friday provides feedback once per week (Fridays) if specifically requested in our OpenGov Public Forum, and we respectfully ask that all proponents of referenda interact with us here for the sake of transparency. Please tag our Head of Protocol Partnerships “Phunky” with your referendum number so that he can gather the relevant commentary from our internal deliberations.

hello @niftesty

it looks interesting. i think it will be more usefull if add documentation about the kind of app that can be used. It´s a good tool but in my case i can´t to undestand how to.. Thanks

@Thibaut I agree. An extendable component library for many polkadot components is part of what UX bounty currently looks for. This proposal is asking for funding on the path of integrating with create-polkadot-app. I know the vite template uses dotconnect so i might just replace my solution with dotconnect and do prs to the dotconnect repo + create-polkadot-app.

@niftesty

Re-building the whole thing (with actually less features) is not what I'd advise for a template though. The idea of a template is to provide a boilerplate with config, and as little code as possible. If some theme isn't great, propose to enhance it maybe? We should absolutely support what's out there, particularly for a template.

@Thibaut thank you for comment. I have seen dotconnect and also saw you are using it in one of your projects. I think it is a very good starter library. But imo the theming options (see screenshot) are limiting. I like the shadcn style of having full control over the components you include in your application. That is why I have not used it there. That said I think it is very good to have multiple open source solutions in an ecosystem devs can work with, but I also value the great set of features and code quality in dotconnect!

wrong account, ignore...

Hey, nice initiative. Just regarding the wallet connection, you should really leverage what's been built already, and go for dot-connect. You get Ledger and WalletConnect out of the box https://dotconnect.dev

I support this proposal! 🚀 The Polkadot Next.js Starter is a fantastic initiative that lowers the entry barrier for frontend developers and junior devs looking to build on Polkadot. Having a solid, easy-to-use starter template will accelerate development, especially for hackathons and new projects in the ecosystem.