Is the concept that you have some persistent buttons on the left hand side for common tasks associated with the app?
Sort of like a dedicated area in the browser that a webapp can add site-wide or page-specific UI controls to, rather than have them anywhere on the page?
Basically, the webapp equivalent of the OS X File Menu or Inspector. That's an interesting concept. Nontrivial chicken and egg problems though in terms of adoption. One approach is a Chrome extension that uses JS to add a "<nav>" element on the left hand side for a select list of sites. The idea is that over time, other sites could adopt this convention and your wrapper might not be necessary.
But are you thinking that you will always want to display these new UI elements in something that is not HTML/CSS/JS? Hmm. Unless you can do some sort of "automatic extraction of UI" from a page...which could actually be super interesting, as the homepage, sign-in button and so on aren't always that easy to find.
That's the sort of thing one could see a browser taking over in a left pane till the site owner got their act together.
Yes, you can use it to expose your key features in unified way the user will understand. You can use it to tie different sites or pages together. Think of apps like "Super Bookmarks" that contain more than one URL.
Comments
Is the concept that you have some persistent buttons on the left hand side for common tasks associated with the app?
Sort of like a dedicated area in the browser that a webapp can add site-wide or page-specific UI controls to, rather than have them anywhere on the page?
Basically, the webapp equivalent of the OS X File Menu or Inspector. That's an interesting concept. Nontrivial chicken and egg problems though in terms of adoption. One approach is a Chrome extension that uses JS to add a "<nav>" element on the left hand side for a select list of sites. The idea is that over time, other sites could adopt this convention and your wrapper might not be necessary.
But are you thinking that you will always want to display these new UI elements in something that is not HTML/CSS/JS? Hmm. Unless you can do some sort of "automatic extraction of UI" from a page...which could actually be super interesting, as the homepage, sign-in button and so on aren't always that easy to find.
That's the sort of thing one could see a browser taking over in a left pane till the site owner got their act together.
Yes, you can use it to expose your key features in unified way the user will understand. You can use it to tie different sites or pages together. Think of apps like "Super Bookmarks" that contain more than one URL.
> Yes, you can use it to expose your key features in unified way the user will understand.
Unified with who? If I'm AnnoyingSocialSites.com's competition, why do I want to unify with them?
Beyond that, what are you providing that can't already be done in a standard browser?
It seems like most of the functionality you're providing is already available in Air or Titanium.
Who is "you"? Are websites supposed to develop their own extensions which will then be embedded into the browser? Or distributed as plugins?
Isn't this basically the exact same thing as pinned sites in IE9?