Book Image

Continuous Delivery for Mobile with fastlane

By : Doron Katz
Book Image

Continuous Delivery for Mobile with fastlane

By: Doron Katz

Overview of this book

Competitive mobile apps depend strongly on the development team’s ability to deliver successful releases, consistently and often. Although continuous integration took a more mainstream priority among the development industry, companies are starting to realize the importance of continuity beyond integration and testing. This book starts off with a brief introduction to fastlane—a robust command-line tool that enables iOS and Android developers to automate their releasing workflow. The book then explores and guides you through all of its features and utilities; it provides the reader a comprehensive understanding of the tool and how to implement them. Themes include setting up and managing your certificates and provisioning and push notification profiles; automating the creation of apps and managing the app metadata on iTunes Connect and the Apple Developer Portal; and building, distributing and publishing your apps to the App Store. You will also learn how to automate the generation of localized screenshots and mesh your continuous delivery workflow into a continuous integration workflow for a more robust setup. By the end of the book, you will gain substantial knowledge on delivering bug free, developer-independent, and stable application release cycle.
Table of Contents (27 chapters)
Title Page
Dedication
www.PacktPub.com
Foreword
Contributors
Preface
Index

Common app rejections


Apple also has a dedicated page that covers many of the common pitfalls developers go through that cause apps to be rejected, as learning from others can help preempt your fate; the page is located at https://developer.apple.com/app-store/review/rejections/. Refer to the following screenshot:

Apple summarizes the most common generic rejection issues as follows:

  • Crashes/Bugs: Apps that are not ready for production and are quite buggy.
  • Broken Links: Apps that provide placeholders or non-functioning links.
  • Incomplete Information: Apps that don’t include demo accounts with enough information for testers to review an entire spectrum of content and functionality. Apps that require a specific environment and that are hard to replicate need to be detailed even further, with videos to demo the hardware.
  • Inaccurate Descriptions: Apps that mislead users, promising certain features or benefits that they won’t or cannot deliver.
  • Poor UX: Apps that provide a poor user experience and interface...