ODO Distributed Online
Breaking News: Proof-of-Concept Prototype released!!
From now on, the ODO project is open for contribution!! Please help!!
What is ODO?
Currently: Work in progress, pre-alpha, available only as proof-of-concept prototype.
What is the Vision behind ODO?
ODO wants to become the “swiss army knife” for the development of distributed communication apps. It will allow developing such apps for various platforms: mobile, desktop, server, maybe even IoT devices. A layered API will allow quick development of simple apps in a low-code-manner, or complex apps using all the features of modern software development environments.
Get rid of Backend Servers
One of the key ideas is to get rid of central servers, meaning the app is really just the app on the device it is running on, no backends, no serers. All data is encrypted and distributed over all devices having ODO installed (using IPFS). This means that an app with ODO can be run with minimal resources on the operator side, as you don’t need AWS, Firebase, Azure or whatever.
Make Privacy and Security easy
One of the main goals of the layered API is to make it easy to develop secure apps with good privacy by design. Of course it is not possible, to have an API which technically prevents all possible security vulnerabilities and privacy problems. But an API can focus on privacy and security, and make these things easy. And while categories of privacy problems arising from a single entity controlling a central server, these kinds of problems simply does not exist with ODO.
Have a closer look at the top level design document for more info about the technical ideas.
When can I have it?
Please be patient ;-) We have the following milestones until the 1.0 release (checked=reached):
- Proof-of-concept Prototype: We have a simple “Hello World” app with a first simple version of the ODO API. This app is distributed via IPFS and can be loaded and run by every ODO installation..
- App: Project Chat: The first useful ODO app should be a simple chat app used by the ODO developers to organize their work. This way, they get a feeling for the API and see, what is needed most badly.
- Pilot Apps: A few pilot apps, covering important basic use cases, should be developed. These pilot apps should cover most parts of the ODO API, so that it is oriented on the practial needs of app developers. These pilot apps could be developed for interested 3rd parties.
- Stable API: Problems in the ODO API are identified and fixed and the API is reviewed and stabilized.
- Release 1.0