API restrictions for apps

[Ramki Gaddipati]

With reference to the blog post made today: http://blog.chromium.org/2012/11/restricting-extension-apis-in-legacy.html, 

I have an app in the store which uses some of the APIs you are planning to restrict. I cannot remove the usage of those APIs. I would like to change the app listing to that of an extension. However, I couldn't find any provision for this. Attempts to upload zip file with an extension manifest were rejected.

 

I wouldn't like to lose my users. 

Could you please suggest a way out?

thanks,

+ramki

[Trevor Squillario]

Yea I fit into this category also. What is the alternative? How does a "legacy" packaged app become an extension?

[PhistucK]

The post reads (ambiguously so, though) -

"Existing legacy packaged apps in the Chrome Web Store will not be affected, and those existing apps can continue to be updated without being subject to these new restrictions."

So, if you already have a published legacy packaged application, you can continue to update it as usual. You will not lose your users.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium Apps" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-apps/-/7VGzRFnk_a4J.
To post to this group, send email to chromi...@chromium.org.
To unsubscribe from this group, send email to chromium-app...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-apps/?hl=en.

[Joe Marini]

Correct, this should not affect existing apps.

--
Joe Marini

Developer Advocate / Chrome

joem...@google.com | +Joe Marini | @joemarini