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
http://techcrunch.com/2011/12/07/forecast-1-billion-html5-phones-by-2013/
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 http://appsfuel.com
7. 3. Developers Friendly
Enabling and creating a profitable HTML5
ecosystem for developers is our priority
Push Notifications Developer Fund
Code Mobile Billing
Library
Tracking & Events &
Stats Workshops
10. Developers Zone
• Free registration
• Free app submission
• No technical requirement,
just enter the URL of your
app and metadata
• Available at
developer.appsfuel.com
• Total Developers: 830
• Total Apps: 548
(as of October 7th)
11. Monetization
Monetization Solutions based on Mobile Operator
Billing, with one-click purchase
• Timed Access
• Paid App
• In App
Purchase
• Subscription
(where approved
by the telco)
12. Developer Tools
• Push Notifications
• Advertising Solutions
• Developer Fund and Events
• Code and graphics Libraries
• And more …
14. We do Scrum
Scrum is an Agile iterative and
incremental method for completing
complex projects.
Originally it was formalized for software
development projects, but works well for
any complex, innovative scope of work.
In a world of constant change we need
constant innovation.
14
15. Scrum in 30 seconds
The product owner creates a prioritized wish list called
product backlog.
During the Sprint Planning meeting, the Team pulls a
small chunk from the top of that wishlist, creating a
Sprint backlog, and decides how to implement those
pieces.
The Team has a certain amount of time, a Sprint - usually
two to four weeks - to complete its work, but meets each
day 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 a
customer, put on a store shelf, or show to a stakeholder.
The sprint ends with a Sprint Review meeting and a Retrospective.
15
16. Time Line
Sprint Planning: the Sprint Retrospective:
team accordingly with the Team looks for ways
the product owner to improve the product
chooses a set of work to and the process
deliver during the sprint
½ day 2 weeks 1h ½ day
Sprint Sprint Review: the Team
demonstrates what it has
completed during the
Sprint
16