Apps fuel oct2012


Published on

Talk alla DevFest2012/Spazio Aziende

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Apps fuel oct2012

  1. 1. AppsFuelThe Open Mobile Revolution Florence, October 2012
  2. 2. HTML5 on Mobile• HTML5 finally introduced a standard for mobile web development• There were 336 million HTML5- capable phones sold in 2011 (Strategy Analytics)• There will be one billion HTML5- capable phones sold in 2013• HTML5 marketplaces are shaping up but not established yet
  3. 3. What is AppsFuel• It’s a new ecosystem for HTML5 mobile web apps• A marketplace available worldwide• Where developers can distribute their apps for free• And earn money via mobile operator billing
  4. 4. Key Differentiating Factors1. Made for Mobile2. Openness3. Developers friendly
  5. 5. 3. Developers FriendlyEnabling and creating a profitable HTML5 ecosystem for developers is our priorityPush Notifications Developer Fund Code Mobile Billing Library Tracking & Events & Stats Workshops
  6. 6. Building BlocksA. MarketplaceB. Developer ZoneC. Monetization ToolsD. Developer Tools
  7. 7. MarketplaceLive in beta at
  8. 8. Developers Zone• Free registration• Free app submission• No technical requirement, just enter the URL of your app and metadata• Available at• Total Developers: 830• Total Apps: 548 (as of October 7th)
  9. 9. MonetizationMonetization Solutions based on Mobile OperatorBilling, with one-click purchase• Timed Access• Paid App• In App Purchase• Subscription (where approved by the telco)
  10. 10. Developer Tools• Push Notifications• Advertising Solutions• Developer Fund and Events• Code and graphics Libraries• And more …
  11. 11. How we work on AppsFuel
  12. 12. We do ScrumScrum is an Agile iterative andincremental method for completingcomplex projects.Originally it was formalized for softwaredevelopment projects, but works well forany complex, innovative scope of work.In a world of constant change we needconstant innovation. 14
  13. 13. Scrum in 30 secondsThe product owner creates a prioritized wish list calledproduct backlog.During the Sprint Planning meeting, the Team pulls asmall chunk from the top of that wishlist, creating aSprint backlog, and decides how to implement thosepieces.The Team has a certain amount of time, a Sprint - usuallytwo to four weeks - to complete its work, but meets eachday to assess its progress (Daily Scrum meeting).Along the way, the Scrum Master keeps the team focused on its goal.At the end of the sprint, the work should be potentially shippable, as in ready to hand to acustomer, put on a store shelf, or show to a stakeholder.The sprint ends with a Sprint Review meeting and a Retrospective. 15
  14. 14. Time LineSprint Planning: the Sprint Retrospective:team accordingly with the Team looks for waysthe product owner to improve the productchooses a set of work to and the processdeliver during the sprint ½ day 2 weeks 1h ½ day Sprint Sprint Review: the Team demonstrates what it has completed during the Sprint 16
  15. 15.