I’m testing a custom component to make a proof of concept before we switch to a paid account. I can see my custom component working in the editor, but when I try to preview the PWA outside the editor using the share link, the component doesn’t appear – and it doesn’t even look as though it’s being called, even when I leave it as the default component that’s created by create-adalo-component. Is this supposed to work, or would it only work on a paid account?
Hey, thanks so much for the reply, this is great news. Is there a way to test the PWA version of the app outside the editor? At the moment, I’m able to view my app on a device just by visiting the preview URL; at the moment, I’d like to be able to deploy to my users just by linking them to a URL rather than requiring them to install an app from the store. However, I’m unable to see my component running on a normal device in that context. How would I usually test a web component on a mobile device?
Sorry, now that I have followed this process through, I see that you’d given me all the information I needed at the start; it just took me quite a while to wrap my head around it! Thank you so much for being patient.
In case anyone else finds this, the information that I took a while to figure out was:
When you run npm start in your new library, your components will appear under “Development” in the editor.
These components will only work in the editor and editor preview. To share them with others, you need to privately publish them.
Once privately published, you need to assign the component to your team, by clicking on the profile icon in the top right corner of your screen, and selecting “Developers” from the dropdown menu (see Managing Private Libraries | Adalo)
If you’re still serving the Developer version, the component won’t appear in the Private list until you turn it off; however, once published, the components will appear in the share webview.