I created cloud-data-module as an experimental library to abstract away use of local storage and logos core modules: messaging and storage, while providing a CRUD interface to interact with the data in a familiar way.
Checkout out the readme (and known limitations). I’m open to small, thought-out PRs.
The library in the cloud data module was integrated into this sample forum sample app.
Curious what others have thought about this.
Background
Once upon a time I tested Google’s AI, Gemini, to one-shot a simple Android app. It worked. I then prompted it to add functionality to store data (deliberately vague to see what path it took)… Google’s Gemini suggested Google Firebase! What a surprise!
In my exploration for better alternatives I came across “web 3.0” (not web3) and work done on Solid Protocol (Socially Linked Data) from Tim Berners-Lee. Which was interesting but unfortunately quite clunky at the time I looked at it.
Around the same time I came across Logos. Basecamp made it easy for a Logos App to use it’s core modules (messaging, storage, blockchain, …), which is a different interface to what a centralised app would integrate:
- Web 2.0 - each app for itself, dependent on a server(s) owned by a single company
- Logos - p2p messaging and distributed storage to recreate the same reliability guarantees
I wanted a web2.0 familiar interface to help devs with data in their Logos apps.