app API model
asked 2014-01-03 20:56:53 +0300
I would like apps to keep an open mind and allow other apps to use services.
For this, i would like a formal API to be created for each app (submitted from harbour?) which follows some sane versioning scheme.
This would allow apps to do interact with other apps.
of course, using such API is not guaranteed to work, and thus apps who use these API will have to check if those services failed or not.
eg:
- games that cross into each-other
- games to auto-find friends from social media
- sky is the limit!
(of course this would also need to be handled security-wise, but that's another post)
Notes:
- it would be nice if this was QML accessible in a simple way
- also Jolla Apps could have API's like this (eg: mail/sms/etc...)
- even the SailFishOS core could have API's like this
Edit: someone mentioned that this is really DBUS. i have no qualms about DBUS nor am i trying to reinvent it. i'm just noting the ideas, if DBUS can/is used for this, then fine. though a formal notation for users and other app devs (and possibly security) is kind of needed (with sane versioning), in order to have stable API's to rely on.
Sounds interesting. This could give interesting cross-working possibilities, but not being a developer, can't really say how feasible this would be. At the least, this should be optional feature and not be enforced for every single app submitted to Harbour. But this was the intention anyways?
pnuu ( 2014-01-03 21:31:34 +0300 )edit@pnuu well, if there's an extra field on harbour app submissions on API, or something, i guess an app could just not fill it in and not export an API to be used from other apps. but sometimes if you do export some API, it ends up being used in surprising ways...
AL13N ( 2014-01-03 21:50:00 +0300 )edit