Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Lean Mobile App Development

You're reading from   Lean Mobile App Development Apply Lean startup methodologies to develop successful iOS and Android apps

Arrow left icon
Product type Paperback
Published in Nov 2017
Publisher Packt
ISBN-13 9781786467041
Length 378 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Authors (3):
Arrow left icon
 van Drongelen van Drongelen
Author Profile Icon van Drongelen
van Drongelen
 Krishnaswamy Krishnaswamy
Author Profile Icon Krishnaswamy
Krishnaswamy
Adam Dennis Adam Dennis
Author Profile Icon Adam Dennis
Adam Dennis
Arrow right icon
View More author details
Toc

Table of Contents (27) Chapters Close

Title Page
Credits
About the Authors
www.PacktPub.com
Customer Feedback
Preface
1. Yes, There Is an App for That FREE CHAPTER 2. Lean Startup Primer 3. Challenges in Applying Lean to Building Mobile Apps 4. An Agile Workflow in a Nutshell 5. A Pragmatic Approach 6. MVP is Always More Minimal Than You Think 7. Minimal Viable Product Case Studies 8. Cloud Solutions for App Experiments 9. Native, Hybrid, or Cross-Platform 10. There Is an API for That! 11. Onboarding and Registration 12. Do Things That Do Not Scale 13. Play Store and App Store Hacks 14. A/B Testing Your App 15. Growing Traction and Improving Retention 16. Scaling Strategies 17. Monetization and Pricing Strategy 18. Continuous Deployment 19. Building an Unfair Advantage 20. The Flyng Case Study 1. Appendix

Timeboxed programming


For each iteration, you need to decide how long it will take and what features will come with it. As you have seen in Chapter 4, An Agile Workflow in a Nutshell, a typical sprint takes 2 to 3 weeks. Although this may be difficult at first, you will learn soon enough what you and your team members can accomplish during such a sprint. Sometimes you will have no clue how long the development of a feature will take. In that case, a timeboxed approach can help you as well. Before you start working on that feature, you allocate a particular amount of time. Afterwards, you can determine what you have accomplished and you can decide whether the feature can be released as it is. Even if it is not completely functional, as long as it contains no (severe) bugs, it can help you to get early feedback.

Keep things simple and develop only the features that you actually need for that particular iteration. You should ask yourself what it is that you want to prove and what feedback you...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images