| |||||||||||||
Mozilla's open web app platformMozilla's open web app platformPosted Dec 10, 2010 19:05 UTC (Fri) by giraffedata (subscriber, #1954)Parent article: Mozilla's open web app platform
under the current paradigm, users have little more than their browser's bookmarking system to keep track of web applications that they frequently use. As a result, web applications remain segregated from the rest of the OS experience — they do not have a persistent presence, they all behave differently in regard to sign-on procedures, and so forth. I see the lack of persistent presence resulting from the user not having a way to keep track of them, but how does different sign-on procedures result from not having a way to keep track of them, and how is different sign-on procedures different from the rest of the OS experience? What is an "installed web app"? I thought a web app was on the web.
(Log in to post comments)
Mozilla's open web app platform Posted Dec 10, 2010 19:41 UTC (Fri) by n8willis (editor, #43041) [Link] I see the lack of persistent presence resulting from the user not having a way to keep track of them, but how does different sign-on procedures result from not having a way to keep track of them, and how is different sign-on procedures different from the rest of the OS experience? For example, when you log in to your user account in a GNOME- or KDE-based desktop, you do not immediately have access to documents that live within the webapps you frequent. (A) because you aren't automatically logged-in to them, and (B) because the session manager lacks both hooks to sign you in to Google/Yahoo/Whatever at login, and a way for you to enumerate which services/apps you'd like to be signed in with. What is an "installed web app"? That's precisely the issue that the Mozilla OWA architecture and manifest spec address.
Mozilla's open web app platform Posted Dec 10, 2010 20:21 UTC (Fri) by giraffedata (subscriber, #1954) [Link] What is an "installed web app"?That's precisely the issue that the Mozilla OWA architecture and manifest spec address. It's not an issue. It's a question -- about a term that appears in the article. I got confused by the various problems and solutions the article talks about. I see analogies made to browser bookmarks, to desktop applications, and to app stores, which are rather different things.
Mozilla's open web app platform Posted Dec 10, 2010 20:35 UTC (Fri) by dmarti (subscriber, #11625) [Link] Related document at Google: Installable Web Apps. "Normal web pages must ask for permission from the user before they can do relatively innocuous things like show notifications, use the clipboard, or access permanent storage. This makes sense; it would be annoying for random web pages you stumble across to show desktop notifications. On the other hand, if a web app repeatedly asks for permission, that's a terrible user experience."
Mozilla's open web app platform Posted Dec 15, 2010 19:06 UTC (Wed) by oak (subscriber, #2786) [Link]
If those apps "host" advertisements (e.g. because they are paid by advertisement) within themselves and those ads would have same privileges as apps but were doneby "random" vendors, that would be terrible security wise though...
Mozilla's open web app platform Posted Dec 15, 2010 2:02 UTC (Wed) by stormypeters (guest, #71843) [Link]
I think of a web app as applications that you log into and you use as an application, but usually within a web page. So for example, gmail, mint, flickr, etc are all "web apps".
Some web apps also have mobile and desktop clients.
|
|||||||||||||