Lessons Learned from How Many Days App Lifecycle

385 days n.w
1 / 5
Embed
Share

Explore insights from the lifecycle of the How Many Days app in "385 Days: Lessons Learned from the Lifecycle of the How Many Days App" by Bret Wardle. Discover essential questions to ask before beginning your app development journey, market entry considerations, necessary documentation, and key learnings for app developers. Uncover valuable tips on navigating non-app tasks, the importance of multiple platform SDKs, market share dynamics, and the significance of efficient development practices.

  • App Development
  • App Lifecycle
  • App Market Entry
  • Mobile Apps
  • Development Insights

Uploaded on | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. 385 Days: Lessons Learned from the Lifecycle of the How Many Days App By: Bret Wardle

  2. Before you begin Questions to ask yourself: Would I use this app? Does it already exist? Do I have the talent to make it? How deep do I want it to go? When do I want to be released? Barriers to entry: Scripting/Programming language SDK and other software Apple Developer Account ($99/Year) Android Developer Account ($25) Scope

  3. Welcome to the market Account Fees Google ($25) Apple ($99/Year) Account Details Developer Name Banking Accounts (If paid App) App Details Name Build Management Description App Approval Icons, Logos, Banners Oh My!

  4. I thought I was making an app Documents (usually websites) Privacy Policy Terms of Use End User License Landing Page Social Media Pages Facebook Twitter Google+ URLs, QR Codes, etc

  5. If theres anything I learned There is always more to add you have to find an exit point So many non-App tasks! Websites Storefront accounts Marketing/Networking Multiple platform SDK is a MUST! 50/50 market share Branching is not cost effective No time for fluff!

Related


More Related Content