search

onflow / developer-grants

Grants for developers that contribute to the broader developer ecosystem
Apache License 2.0
50 stars 18 forks source link

Flow NoCode Apps - Revised #99

Open iwe90 opened 2 years ago

iwe90 commented 2 years ago

Grant category

Developer tools / services ( & Educational material)

Description

We plan to create NoCode Apps for the Flow Ecosystem so that everyone (not only developers) can access, work & interact with the Flow Blockchain Ecosystem.

Problem statement

Accessing data from the blockchain can be a complex process and pose a challenge especially to users who are not proficient coders. For instance, accessing individual transaction data is possible via individual display options, but tiresome and may not provide a useful format that non-coders can creatively and flexibly use.

Proposed solution

In other contexts involving large-scale data queries and data management, NoCode tools have been gaining in popularity. Our plan is to build a set of NoCode modules for the Flow ecosystem. By the popular NoCode platform Make, we will create an accessible entry for both casual users and potential new developers. Overall, the resulting NoCode modules have to potential to make Flow even more attractive to both users who are new to the blockchain technology and developers who want to generate creative solutions fast.

Demo Video: https://www.loom.com/share/7dac988f02ef4505be22a37382bc6a37

Additional info revised version: We originally submitted a larger proposal comprising more modules, but after consultation with @alxflw, we revised and reduced it to a smaller initial project. This will allow us to evaluate how the apps do within the community and potentially continue from there.

We have now already systematically evaluated the available NoCode platforms which we could potentially build on and decided that Make is the most ideal plaform for this purpose. This is because 1) it is one of the largest NoCode platforms (500.000+ users), 2) the cost of individual operations is very low (e.g., compared to Zapier), 3) it is very accessible, 4) it is highly flexible when it comes to the integration of several modules into complex workflows, which is helpful when programming some of the envisioned workflows for the flow ecosystem.

Impact

The aim is to make the modules and the resulting solutions available and accessible to literally everyone in the Flow community- and to everyone interested in joining it. Every single community member will be enabled to quickly and easily build dashboards, tracking apps, tax apps, notification apps, Discord bots and much more, either for personal use or for broader use across the entire community.

Milestones and funding

Milestone Deliverables Timeline Risks USD proposal
1 - Ecosystem Research List of NoCode solutions to build based on community research, i.e. talking to a number of interested Flow companies/projects to find out which solutions may be most helpful to them. 3 weeks - -
2 - Development of modules Develop selected NoCode apps, e.g., get transaction, get token holder list for token, get wallet information. 6 weeks - 8,000
3 - Creation of workflow templates Create three exemplary workflows based on the results of our community research, e.g., NFT/Token Dashboards, transactions export/import into tax software, whitelist of token holders, daily commission earned through secondary sales. 2 weeks - 2,000
4 - Publication of modules & workflows Once created, the modules will be made available using a public URL and published officially on Make. The workflows will also be published as templates for everyone to use. continuously - -
5 - Educational content Creation of educational content on how to use apps and workflows, e.g., blogposts or videos. 4 weeks - 3,000
6 - Adoption 100 people use the developed models. 8 weeks after completion - 2,000

Team

Name Role Bio Contact
Ivonne Project Lead Ivonne is currently doing her PhD in cognitive Science and has a background in scientific programming and cross-discipline communication. Ivonne.weyers@gmail.com
Richard Lead Developer Richard is a NoCode power-user who has developed several custom apps before. He recently finished his Master's degree in Finance and has been in love with DeFi since then. Richard.Ahrend@gmail.com

Together, we understand the challenges of complex new technologies and would love to make Flow more accessible to everyone.

chrisackermann commented 2 years ago

Thanks @iwe90! We'll review and get back to you shortly.

chrisackermann commented 2 years ago

Hi @iwe90 - thanks again for your proposal!

We're reviewed and have a few follow-up questions/comments:

Thanks!

iwe90 commented 2 years ago

Hi @chrisackermann , thank you very much for your feedback!

With regard to your first question: We are planning on announcing the Flow NoCode modules on a newly set-up Twitter and on a blog, where we will also post the educational content on how to use them. We will also ask the flow native projects which we plan on collaborating with (Milestone 1) to share some information in their respective channels highlighting their practical use of the modules. This will be particularly useful for other projects to adopt similar workflows. The publication of the apps on Make is not trivial either, because newly published apps are usually announced in their monthly review. Additionally, we are going to draw attention to the new apps by posting about them in the Make Community channels (forum and Slack), so that fellow NoCoders can have a sneak-peak into flow. All of this should allow for these first few modules to reach fellow builders and explore even more use cases! :)

With regard to your second question: Do you want this milestone to include a specific number of people that have used/viewed the developed solutions? And do you want a specific USD amount to be assigned to this milestone and for this to be conditional on reaching this number? Or do you mean a more general milestone like “usage tracking” that is more exploratory and unconditional?

chrisackermann commented 2 years ago

Hi @iwe90, thanks for the additional context! It's super helpful to better understand how others will discover the modules, thanks for that.

With regard to your second question: Do you want this milestone to include a specific number of people that have used/viewed the developed solutions? And do you want a specific USD amount to be assigned to this milestone and for this to be conditional on reaching this number? Or do you mean a more general milestone like “usage tracking” that is more exploratory and unconditional?

We're looking for the former - for example, a milestone such as 'X people using the modules' and a USD amount for reaching that milestone.

iwe90 commented 2 years ago

Hi @chrisackermann, thank you for the quick reply. Regarding the additional milestone- could you help us with the numbers here? How many people using the modules would you consider a success in the context of this small initial project?

chrisackermann commented 2 years ago

Hi @iwe90 - perhaps 100 people would be a good indicator of impact from this project?

iwe90 commented 2 years ago

@chrisackermann sounds good! I added the number to the milestone & added a timeframe as well.

chrisackermann commented 2 years ago

Hi @iwe90 - thanks for the updates and for your patience! Just wanted to let you know that we've accepted your proposal and will be following up directly on next steps. Thanks!

iwe90 commented 1 year ago

@chrisackermann I made the minor changes to Milestones #2 and #3 as suggested in our last e-mail.