I’d like to request a feature that allows private custom components to be locked to a single app or account, preventing them from being shared with other apps or teams.
As a component developer, I sell custom components directly to clients because I can’t use the Adalo Marketplace. Stripe isn’t available in many South American countries, so publishing components on the Marketplace isn’t an option for us.
The current issue is that once I add a private component to a client’s app, there’s no protection against that component being shared or redistributed. Someone could purchase it once and then share it with other accounts, making it very difficult for developers to protect their work.
This feature would help developers safely sell private components while protecting their intellectual property.
Also, if anyone has found a workaround or another way to prevent private components from being shared, I’d really appreciate your advice.
@Dilon I can’t list on the marketplace because my LLC hasn’t been activated yet to use Stripe… it’s not used in South America, so I’ll have to sell them individually using USDT… but if I share them as a member, they can give them to others… how can I prevent the user I give the component to from using it on other accounts, like those purchased on the marketplace?
Adalo should transact with developers, directly. Not a marketplace.
More control. Better quality. Less money burnt on the wrong component ( I wasted at least $50 on components, with b.s. support, and it wasn’t transferable to a new account ) Consistent standards standards. etc.
I hear all this talk about consistency in design… try comparing component options in the Adalo market place. There is little-to-none. I doubt it’s any one developers fault.
There is zero regulation of enforcing developers to keep their apps up to date, and it has caused me client issues and more work as I have to eliminate the private components to make my app function again. Components that I paid for. If there is an issue with a component, that ADALO approved, ADALO should handle the issue and communicate with the developer, and not make their customer communicate with their third party developer who has no required updates. Even worse, telling my clients what I implemented is no longer doable. Reminds me of WordPress and their numerous plugins required to make a blog platform a functioning website.
I have several published apps (iOS and Android) on ADALO for the record. 8 to be clear. I’m just losing confidence that the tech progress is falling way behind, very quickly. I really hope things get better in the near future.
Regarding the original request from Santiago, it’s on our radar but it’s a bit low priority at the moment. With the incoming upgraded AI builder, you can easily create components with prompts quicker, stay tuned for more information!
Team main priority right now is getting out the new AI builder that solves most of the issues, which will come out in the following weeks. Currently it’s being tested by the team and fixing those issues, then let friends of Adalo to test out and give us feedback (Experts, Community Leaders, and possibly more beta testers from the community..), and then make it available for all the makers.