5 ms·

Hello, my name is Aaron, and I will be your question answerer for today. - Anything that works in Chrome can be an app. Flash apps are OK (one of the demo apps

Hello, my name is Aaron, and I will be your question answerer for today. - Anything that works in Chrome can be an app. Flash apps are OK (one of the demo apps at the keynote, Plants vs Zombies, was a flash app) - We haven't finalized exactly how payments will work. We know it has to be good, because it needs to be better than what you could do yourself. - The web apps in the store will most likely work with Mozilla, Opera, Safari, etc, because those are pretty modern browsers that implement most of HTML5. But the tight integration with Chrome (the "install" experience) is Chrome-only, at least for now.

glhaynes 16y ago
I don't understand the last point: if I can only purchase and install them from Chrome, how do I run them in another browser? Just point the non-Chrome browser at the (un-DRMed?) local install after purchasing/installing with Chrome?
- aboodman 16y ago
  Apps are essentially a metadata wrapper around a URL^. The payment authorization is done server-to-server. Thus you could buy an app in Firefox and authorization would still work fine, the UX just won't be as nice. ^ We are also considering supporting fully packaged apps that are completely offline, like Chrome extensions are today -- these won't work in other browsers because they don't understand our package format.
  - warfangle 16y ago
    Will you make the spec for the package format open, so other browsers would be able to implement support for fully packaged apps?
    - aboodman 16y ago
      All of chrome is open source and the format is already documented -- other browsers are welcome to implement it, or just take the code if they want.
  - blasdel 16y ago
    Using bundled packages for offline support is entirely the wrong strategy. The coupling is too tight even before you start trying to use the same format for multiple browsers. You should just copy Apple and just make it easy to save web pages as local apps, though you might want to explicitly offer with an infobar when there's a manifest available. What they already look for is all you need: <html manifest="..."> and window.applicationCache <meta name="application-name"> and <meta name="application-url"> <link rel="icon" sizes="..."> or <link rel="apple-touch-icon">
    - papachito 16y ago
      Here they explain how they do it http://code.google.com/chrome/apps/docs/developers_guide.html#live http://code.google.com/chrome/apps/docs/developers_guide.htm...
      - blasdel 16y ago
        The capability model for requesting extra permissions is terrific, but it should have been done using <meta> or <link> tags -- reusing their bundle format for extensions was a terrible idea, especially since they're going to have to implement all the DOM-based stuff anyway.
deleted 16y ago
[deleted]
fjabre 16y ago
Payments would be tricky I'd think. Take apps like Highrise or Mailchimp for example. They already have their payment backends working just fine. Would they be forced to integrate with a Google pay system if they wanted to get into the store?
- aboodman 16y ago
  I think they would just post their app as "free" in the store and handle payments themselves. Or support both payment systems if the distribution is worth it to them.
DenisM 16y ago
Please make sure to support subscriptions. Thanks.
trimagination 16y ago
When is the replacement for Gears going to be released? I really miss it :(
- blasdel 16y ago
  Gears was the alpha implementation of the work that went on in WHATWG. All the Gears APIs (except for WorkerPool) were refactored significantly and integrated into the spec that became HTML5.
83457 16y ago
Will there be support for one login to multiple apps? Would be useful to essentially have a Chrome Apps login that then provides auto-login/off for the other apps installed on Chrome
- aboodman 16y ago
  This is something we're interested in too. Unclear if it will be in v1.
  - papachito 16y ago
    Is there any release date for the store and payment system? Will it only work with a few countries like google checkout?
Detrus 16y ago
What about the NativeClient and Unity3D apps in other browsers? Users will have to have NaCl installed as a plugin?

glhaynes 16y ago

I don't understand the last point: if I can only purchase and install them from Chrome, how do I run them in another browser? Just point the non-Chrome browser at the (un-DRMed?) local install after purchasing/installing with Chrome?

aboodman 16y ago
Apps are essentially a metadata wrapper around a URL^. The payment authorization is done server-to-server. Thus you could buy an app in Firefox and authorization would still work fine, the UX just won't be as nice. ^ We are also considering supporting fully packaged apps that are completely offline, like Chrome extensions are today -- these won't work in other browsers because they don't understand our package format.
- warfangle 16y ago
  Will you make the spec for the package format open, so other browsers would be able to implement support for fully packaged apps?
  - aboodman 16y ago
    All of chrome is open source and the format is already documented -- other browsers are welcome to implement it, or just take the code if they want.
- blasdel 16y ago
  Using bundled packages for offline support is entirely the wrong strategy. The coupling is too tight even before you start trying to use the same format for multiple browsers. You should just copy Apple and just make it easy to save web pages as local apps, though you might want to explicitly offer with an infobar when there's a manifest available. What they already look for is all you need: <html manifest="..."> and window.applicationCache <meta name="application-name"> and <meta name="application-url"> <link rel="icon" sizes="..."> or <link rel="apple-touch-icon">
  - papachito 16y ago
    Here they explain how they do it http://code.google.com/chrome/apps/docs/developers_guide.html#live http://code.google.com/chrome/apps/docs/developers_guide.htm...
    - blasdel 16y ago
      The capability model for requesting extra permissions is terrific, but it should have been done using <meta> or <link> tags -- reusing their bundle format for extensions was a terrible idea, especially since they're going to have to implement all the DOM-based stuff anyway.

deleted 16y ago

[deleted]

fjabre 16y ago

Payments would be tricky I'd think. Take apps like Highrise or Mailchimp for example. They already have their payment backends working just fine. Would they be forced to integrate with a Google pay system if they wanted to get into the store?

aboodman 16y ago
I think they would just post their app as "free" in the store and handle payments themselves. Or support both payment systems if the distribution is worth it to them.

DenisM 16y ago

Please make sure to support subscriptions. Thanks.

trimagination 16y ago

When is the replacement for Gears going to be released? I really miss it :(

blasdel 16y ago
Gears was the alpha implementation of the work that went on in WHATWG. All the Gears APIs (except for WorkerPool) were refactored significantly and integrated into the spec that became HTML5.

83457 16y ago

Will there be support for one login to multiple apps? Would be useful to essentially have a Chrome Apps login that then provides auto-login/off for the other apps installed on Chrome

aboodman 16y ago
This is something we're interested in too. Unclear if it will be in v1.
- papachito 16y ago
  Is there any release date for the store and payment system? Will it only work with a few countries like google checkout?

Detrus 16y ago

What about the NativeClient and Unity3D apps in other browsers? Users will have to have NaCl installed as a plugin?