At present the workflow for granting access to a DA app goes something like this:
- User does something that requires app to request DA access
- App directs user to DA auth page, providing the OAuth request token
- User enters MySpace login details and submits
- On successful authorization user's browser is redirected to app callback page, where app can then request the OAuth access token for that user
- App goes on its merry way and requests the necessary data through DA
This currently works fine if you are a developer of an app. However if you aren't a developer you get bounced to the MySpace user home page after you enter your details (previously you got a message saying you need to be a developer of the app).
This implies that DA apps need to be published or somehow put into a non-developer state in order for other users to access it. At present the only visible mechanism for doing that is the Publish button, which of course doesn't work because the publication process expects there to be panels (which won't exist).
The only way to tell the process that there aren't any panels is to mark the installable checkbox as unchecked - which is what you suggest in your blog post on Jul 19 (http://developer.myspace.com/Community/blogs/devteam/archive/2008/07/18/about-that-installable-checkbox.aspx).
What does installable mean?
Installable means that the app can be added to
your users' home/profile surfaces. It also means that it is an
Opensocial app, as opposed
to an external app, (which has installable unchecked). Installable
identifies the app as external for Data Availability.
Which would be fine if the checkbox actually stayed unchecked
As mentioned previously this app has never previously gone live, so I can't see why it keeps coming up as installable.