I think we've got a great list of things collected here from the standpoint of the end user interaction as well as browsers vendors. What I haven't seen being captured in one single place, which IMHO is part of this effort, are the possible web application architecture(s), patters and guidelines and what is currently possible with IPFS in the browser from the stand point of building an app. I know this might feel unrelated to the current effort, but IMHO it is.
I see two points worth capturing and expanding:
How would you build an IPFS enabled web app currently?
What can you serve from IPFS and what has to be served over good'ol HTTP
...
What would be the ideal support required from the browser and ipfs itself to build the next gen web apps?
This is heavily discussed in this repo, but not consolidated under an issue that someone evaluating the technology can use to gain a clear understanding of what this offers him/her as an app developer/vendor.
How is this relevant to browser vendors?
Its relevant to know which primitives the browser already offers and how they can be used with IPFS, their possibilities and limitations - i.e. ServiceWorkers, etc...
We need to be able to say what are the ideal IPFS primitives required and what the next gen apps would look like (pretty ambitious, but worth thinking about in this context)
The above will also allow understanding better what would be the transition path web app developers would need to follow to get from whats currently possible without native support to what will be possible once native support is there.
If this sounds like something worth discussing, I suggest we get on a call to further discuss it and capture the outcome here later on.
dryajov commentedApr 18, 2017
•
edited
I think we've got a great list of things collected here from the standpoint of the end user interaction as well as browsers vendors. What I haven't seen being captured in one single place, which IMHO is part of this effort, are the possible web application architecture(s), patters and guidelines and what is currently possible with IPFS in the browser from the stand point of building an app. I know this might feel unrelated to the current effort, but IMHO it is.
I see two points worth capturing and expanding:
How is this relevant to browser vendors?
If this sounds like something worth discussing, I suggest we get on a call to further discuss it and capture the outcome here later on.
@flyingzumwalt @lgierth @diasdavid @kyledrake @kumavis @Gozala @haadcode
(apologies if this has been already discussed elsewhere - I couldn't find anything in specific in this repo)
The text was updated successfully, but these errors were encountered: