Consider a procedural API for a future iteration

WICG / file-handling

API for web applications to handle files

Other

82 stars 15 forks source link

Consider a procedural API for a future iteration #18

Open raymeskhoury opened 5 years ago

raymeskhoury commented 5 years ago

Thomas Steiner:

Could file_handler be dynamically extended, without pushing a new manifest? Conceived-ish example: you have a freeium app that initially handles just .foo files, you install it, love it, unlock the premium version, and now it can also handle .foopremium files.

Good thought. I think we should add that as something to explore for V2. The same idea has been raised for the proposed Shortcuts API and it's also relevant for web share target - ideally these "handler" APIs should have declarative and procedural versions

fallaciousreasoning commented 5 years ago

Interesting idea. You could achieve something similar by pushing an update to the manifest (based on cookies or sessions or something).

Do you think in this kind of situation, the app would want to be associated with .foopremium files anyway (so they can prompt the user for the upgrade)? This is what Word, Visual Studio, Intellij and the like do when you don't have a valid license.

But its definitely a neat idea to explore for V2.