As explained in the previous article in the series, building an no-code based solution in web3 is the major bridge of the various ecosystem and creation of the necessary value creation of the workflow economy, but what are the challanges the current versions of the web3 equivalent tools are facing in order to scale the event driven systems across different chains, i will be explaining in this short article.

taking the leaf out of the current no-code solution stack , major no-code solutions that are either domain specific (for instance DeFI for furocombo to more general web3 solutions like buildlHub (which is btw defuncted to its current version dexible)). these solutions had being facing mixed results due to the following challanges

• not having the incentives to maintain the availability of the service : lets face it, even though with significant development of client softwares , adapter hooks and other services to easily onboard the current web apps into Dapps , the availablity of the service guarantees of the core blockchain service providers (which is indeed the current web2’s only strong point against the growing calls of noCloud ecosystem ) is still not reliable when it comes vis a vis their corresponding counterparts , thus facing issues specially when it comes to building workflow driven applications . current closed source solutions on the other hand have very high leverage as they get superbe support by the host companies guarenteed in form of SLA contracts , 24/7 response to the resolution of the issues .

• not having strong incentive mechanisms when it comes to building the general event driven architecture : currently major giants in the space (Zapier ,IFTTT, Airtable, webflow) have the benefits of their core services (on which they build the wrapper services )are already major services providers (google , adobe , meta , aws etc)but are used modularly in the different contexts / genres in the todays corporate enviornment (CRM’s, ERM’s…… being unified as one ) . and thus their renevnues is secured by the monthly subscription of the clients as well as the referal bonue by the base service providers

if the tokenomics of getting an well maintained no-code dapp service into web3 is being redefined, this holds great potential for web3 based workflows . the potential for building the stable stream can be DeFI mechanisms (like having defi protocol support that will build LP pairs of these different service providers underlying tokens and providing stable subscription protocols ).

• hiring competent dev and product managers: to understanding the wide variety of the verticals of these services and how the end user (being the current talent of non IT people onboarding to this open ecosystem as smoothly possible ). companies like pro

the challenges explained above are one of the prominent ones that indeed can be addressed considerably thanks to the organic nature of the stellar growth of the web3 ecosystem startups / communities with great emphasis on both the aspects of the product design from the frontend applications (deepwork) to experienced developer communities (dORG , metacartel rail guild , developer DAO) and then to understand the convey the user requirements for the given use case (product house)

thats if for the short article , hope you got interested in the paradigm shift of automated events that web3 ecosystems will be benefiting thanks to the no-code/low-code ecosystem , from the upcoming tutorials i will be getting more in-depth analysis of the current tech .

Thanks for reading and feel free to share your viewpoints on @lesDecroissant on twitter .

split://0x46ed2A88D9F786EA233d0D783847e0a2502dA101

crowdfund://0x46ed2A88D9F786EA233d0D783847e0a2502dA101?features=

As explained in the previous article in the series, building an no-code based solution in web3 is the major bridge of the various ecosystem and creation of the necessary value creation of the workflow economy, but what are the challanges the current versions of the web3 equivalent tools are facing in order to scale the event driven systems across different chains, i will be explaining in this short article.

taking the leaf out of the current no-code solution stack , major no-code solutions that are either domain specific (for instance DeFI for furocombo to more general web3 solutions like buildlHub (which is btw defuncted to its current version dexible)). these solutions had being facing mixed results due to the following challanges

• not having the incentives to maintain the availability of the service : lets face it, even though with significant development of client softwares , adapter hooks and other services to easily onboard the current web apps into Dapps , the availablity of the service guarantees of the core blockchain service providers (which is indeed the current web2’s only strong point against the growing calls of noCloud ecosystem ) is still not reliable when it comes vis a vis their corresponding counterparts , thus facing issues specially when it comes to building workflow driven applications . current closed source solutions on the other hand have very high leverage as they get superbe support by the host companies guarenteed in form of SLA contracts , 24/7 response to the resolution of the issues .

• not having strong incentive mechanisms when it comes to building the general event driven architecture : currently major giants in the space (Zapier ,IFTTT, Airtable, webflow) have the benefits of their core services (on which they build the wrapper services )are already major services providers (google , adobe , meta , aws etc)but are used modularly in the different contexts / genres in the todays corporate enviornment (CRM’s, ERM’s…… being unified as one ) . and thus their renevnues is secured by the monthly subscription of the clients as well as the referal bonue by the base service providers

if the tokenomics of getting an well maintained no-code dapp service into web3 is being redefined, this holds great potential for web3 based workflows . the potential for building the stable stream can be DeFI mechanisms (like having defi protocol support that will build LP pairs of these different service providers underlying tokens and providing stable subscription protocols ).

• hiring competent dev and product managers: to understanding the wide variety of the verticals of these services and how the end user (being the current talent of non IT people onboarding to this open ecosystem as smoothly possible ). companies like pro

the challenges explained above are one of the prominent ones that indeed can be addressed considerably thanks to the organic nature of the stellar growth of the web3 ecosystem startups / communities with great emphasis on both the aspects of the product design from the frontend applications (deepwork) to experienced developer communities (dORG , metacartel rail guild , developer DAO) and then to understand the convey the user requirements for the given use case (product house)

thats if for the short article , hope you got interested in the paradigm shift of automated events that web3 ecosystems will be benefiting thanks to the no-code/low-code ecosystem , from the upcoming tutorials i will be getting more in-depth analysis of the current tech .

Thanks for reading and feel free to share your viewpoints on @lesDecroissant on twitter .

split://0x46ed2A88D9F786EA233d0D783847e0a2502dA101

crowdfund://0x46ed2A88D9F786EA233d0D783847e0a2502dA101?features=