5 ms·
It took a little while but I'm thinking the main point here is that you store your content in the Osmek system. Then the content can be published to multiple s
by ashray 13y ago
It took a little while but I'm thinking the main point here is that you store your content in the Osmek system.
Then the content can be published to multiple sources such as an iOS app, website, tablet app, mobile website.
I just don't understand how this is different from having your own database with the content. What's the difference between this and say Django's auto generated admin interface (setup with proper permissions) ?
Why can't my apps just pull stuff out of the database or through my own API ?
I'm sure I'm missing something because this seems expensive so it must be worth a lot to somebody. But why ?
- roc 13y agoThis seems to be a centralized content store for people without the time/money/expertise to roll their own. The big unaddressed question is that most of the targets people care about aren't publish-only. Managing changes/submissions from many publishing targets [1] is one of those deceptively non-trivial tasks. [2] [1] each with their own inconsistencies, permissions issues, etc. [2] Not unlike dropbox's client software. It sounds easy. But try writing it.
- lifeformed 13y agoI still don't quite get it. Can you provide an example? Let's say I want to make a shared blog with Osmek. My writers use Osmek's interface to write articles, and I use the API to get the articles into blog? So it's storing the article content and it's metadata for me?