409
edits
Dclarke
Joined 11 July 2011
no edit summary
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
Date: 08/17/2011<br> | Date: 08/17/2011<br> | ||
== Overview == | == Overview == | ||
Open Webapps is a fairly overloaded term, but basically incorporates a few main pieces of infrastructure. | |||
*An App Store (based off of AMO) | '''Open Webapps is a fairly overloaded term, but basically incorporates a few main pieces of infrastructure.''' | ||
**Paypal Chained API for payments | |||
*A set of Web API's that can be loosely defined as our App Cloud | *An App Store (based off of AMO) | ||
**Paypal Chained API for payments | |||
*A set of Web API's that can be loosely defined as our App Cloud | |||
*A browserID integration | *A browserID integration | ||
The devices that will interact with the system are initially to be | |||
*Desktop (Windows / Mac) | '''The devices that will interact with the system are initially to be''' | ||
*Mobile (Android /iOS) | |||
*Desktop (Windows / Mac) | |||
*Mobile (Android /iOS) | |||
*Tablet (Android /iOS) | *Tablet (Android /iOS) | ||
The purpose of this system is to serve as a way for HTML5 based apps to be distributed, across multiple devices. <br> | |||
Community Involvement <br> | |||
I see community involvement being a good way to do exploratory testing, gather usability feedback, as well as determine ease of use of the store / apps / widgets ..etc. The ability to test installs / usage patterns across multiple operating systems / tablets / phones could be very helpful. | |||
== Desktop == | == Desktop == | ||