How can i create a library of optional extras for my plugin

Hello, hoping that what I'm looking for exists. Im building a rather large website about wildlife (and travel to see it).

I have built a live sightings board for the limpopo transfrontier park, and a few other destinations.

What i an looking for, is the ability to make these destinations essentially addons to the app. As i build this feature for more and more destinations, the app could get too big,
so i want to be able to offer the destinations as additional extensions to the app, so they can simply be downloaded and added as needed.

I hope someone can help with a method to do this. Any help greatly appreciated (i can imagine a wide array of uses for this)

Hello TimWelby,
what you are looking for exists. You can do this very easily by using the CloudDB component (in the appinventor´s „storage“ tab) that enables you to store text (strings and so on) under tags on the MIT or your own Server and, if you have pictures included, an extension that converts pictures to text (strings) since only they can be stored like this ([Free] Base 64 extension. File to/from Base 64), so you can download the contents if needed.
If you have further questions, feel free to ask me and the other community members :slight_smile:

1 Like

Thanks for the prompt answer, I'll have s look, and see if that works. I've had a thought, which might well avoid the issue for now (we've offloaded the actual sightings board to our website, so it's merely a list of destinations, with a list of animals for each)

Things will start here, and how you are storing each individual sighting record. Once we know that, along with probably some other requirements..., we should be able to advise on the best way forward.

Also, are you building an app, or just loading your website into the app? If the latter, it would probably take us outside of the AppInventor realm, and be more about web...

1 Like

Hi yes, i have been building the app. The issue I'm facing, is that generally wild animals are found far away, so I'm trying to create an app that requires as little data as possible, with a many features usable without as possible.

I realize for some of the website features, just direct link to the website would be easiest.

We have set it up, so that the sightings board can be used locally for your own personal sightings, as well as using it online so you can access other people's historical data.

In particular, my app so far, offers the ability to save a sighting for future uploading, when signal exists