Skip to main content

Apples Instructions for Submitting your iPhone/iPod touch Demo Application

  1. Demo versions of your shipping application cannot have any type of log-in, account, password, ability to save a player's name, etc.
    Please note: This is a VERY important requirement.
    • If your shipping application requires users to log-in to an account, please create a demo app that upon launch is already logged-in to an account that contains demo data.
    • If you use demo data, make sure that it is fully licensed for your use. (For example, don't use the names of characters from the latest hit movie.)
    • Make sure to disable logins to all third-party accounts, including Facebook, Twitter, etc. For games, remember to disable the login to the online "leader board."

  2. For features that you are disabling for the demo, please include a popup alert that states, "Feature not enabled for this demo."
    Please localize this message for all of the languages the app supports.
    • For example, if your shipping app enables users to purchase additional game levels, the demo should let the user to get to the point of purchasing and then see a popup alert that states "Feature not enabled for this demo"
  3. If the full version of your application is available on the App Store as a Free App, please go to step 5.
  4. If your app is listed on the App Store as a Paid App, please complete these additional steps:

    • Create a version of your application for demonstration purposes.
    • Include a splash screen that indicates this is a demo version of your full product and use the following text: "This version of  has been created specifically for demonstration purposes."
      • Please localize this message for all of the languages in your demo.
    • Ensure the icon for this demo version is identical to that used in the shipping paid App.
    • Name this application exactly as it currently appears on the App Store 
    • When your demo app is installed on an iPhone or iPod touch, it must look exactly as if a customer were to download your paid app from the App Store, with the same exact name and icon.
  5. Make sure that your demo app provides the same localization as your currently shipping app.
  6. Build your demo app and verify that it successfully installs on your development device.
  7. Make sure that your demo app, when installed, looks exactly like your shipping application: the same icon with the same app title under the icon.
    • REMEMBER: This version of your app must have been thoroughly tested on a device running iOS 4.3.3.
  8. Build a Distribution version of your demo app and sign it using your distribution certificate. Send the binary built in .ipa format.
  9. Make sure that the demo app you send us has the exact same name as the official name of your app on the App Store.
  10. Send the files compressed in .zip format in the naming format: "DEVELOPER NAME - APP NAME.zip" exactly as they appear on the App Store.
    • For example: "Acme Inc - Touch Fighter.zip".
  11. Make sure that the subject of your email contains the exact same name as the official name of your app on the App Store.
  12. Email the zipped demo app to ***@apple.com. If the zipped demo app is too large to email, please provide an ftp server location with login information for us to download your demo app.

Comments

Most Favorite Posts

Firebase realtime database stability - and monitoring

Firebase SLA Firebase will use commercially reasonable efforts to make Firebase available with a Monthly Uptime Percentage (defined below) of at least 99.95%, in each case during any monthly billing cycle (the "Service Commitment"). Firebase SLA Service Level Agreement for Hosting and Realtime Database Firebase Status Page Why Firebase sucks In the 3 years since starting to use Firebase we’ve suffered from so many outages I’ve literally lost count. @ Medium.com Status History Overview Statusgator Does anyone has real-life experience with the stability of Firebase or Firestore? Please leave a comment! We heared that Firestore is much more stable than Firebase which usage for new project is discouraged...

Validity Time Auto-Renewables in Sandbox

The subscription durations, sandbox durations and incentive durations of auto-renewables. Hint: In Sandbox the validity time differs from live environment!!! Durations Sandbox Duration Incentive Durations (optional) 7 days 3 minutes 7 days 1 month 5 minutes 7 days, 1 month 2 months 10 minutes 7 days, 1 month 3 months 15 minutes 1 month 6 months 30 minutes 1 month, 2 months 1 year 1 hour 1 month, 2 months, 3 months After 6 extensions the abo is cancelled automatically in the sandbox environment.

Backend-driven native UIs

Backend-drive native UIs John Sundell  Slide Share Using Back-End Design to Create Customizable Front-End Mobile Experiences By controlling the front end of mobile apps from the back end we can build customized experiences at runtime, creating cleaner interfaces and reducing load times. Nithin Rao UX Magazine The Hub Framework Welcome to the Hub Framework - a toolkit for building native, component-driven UIs on iOS ( no Android support released yet ). It is designed to enable teams of any size to quickly build, tweak and ship new UI features, in either new or existing apps. It also makes it easy to build backend-driven UIs. The Hub Framework has two core concepts - Components & Content Operations. Spotify LeeGo: Build UI without UIView LeeGo is a lightweight Swift framework that helps you decouple & modularise your UI component into small pieces of LEGO style's bricks, to make UI development declarative, configurable and highly reusable. Wang Shen...

Understanding Automatic Reference Counting in Objective-C

Automatic Reference Counting (ARC) largely removes the burden of manual memory management, not to mention the chore of tracking down bugs caused by leaking or over-released objects! Despite its awesomeness, ARC does not let you ignore memory management altogether. This post covers the following key aspects of ARC to help you get up and running quickly. Reference Counted Memory: Quick Revision How Automatic Reference Counting Works Enabling ARC in Your Project New Rules Enforced by ARC ARC Qualifiers – Declared Properties ARC Qualifiers – Regular Variables Migrating Existing Projects to ARC Including Code that is not ARC Compliant Should I Use ARC? The Long Weekend Website

JSLint

Many JavaScript implementations do not warn against questionable coding practices. Yes, that's nice for the site that "works best with Internet Explorer" (designed with templates, scripted with snippets copied from forums). But it's a nightmare when you actually want to write quality, maintainable code. That's where JavaScript Lint comes in. With JavaScript Lint, you can check all your JavaScript source code for common mistakes without actually running the script or opening the web page. JavaScript Lint holds an advantage over competing lints because it is based on the JavaScript engine for the Firefox browser. This provides a robust framework that can not only check JavaScript syntax but also examine the coding techniques used in the script and warn against questionable practices. JavaScript Lint Online Form

Automating Over The Air Deployment for iOS

Over the air deployment is based on a new command in the build menu of Xcode called “build and archive” which packages the application with an embedded provisioning profile. There have been many questions on how to integrate this feature in a continuous integration process. The “xcodebuild” command is well known : it builds an Xcode project from the command line and generates an “.app” file. You can use this command to build your application from a script ran by a software factory. But the generated file cannot be distributed over the air since it misses the embedded provisioning profile. We need to build the project into an “.ipa” file, containing the provisioning profile and signed with your developper identity. To be able to find the command line, the trick was to watch the system console log while running a “build and archive” through Xcode. #!/bin/sh # build.sh # # Created by Vincent Daubry on 19/01/10. # Copyright 2010 OCTO. All rights reserved. PROJDIR=${WORKSPACE...

TechLead: React Native vs Flutter vs WebView - Hybrid Mobile App Development for 2018

Topics covered: Xamarin, Cordova, Flutter, Titanium, React Native, Flutter React Native Web Views Native Development: iOS and Android Types of apps: Fully native high interactivity expensive: iOS and Android high interactivity, personalization, performance worth for top 50 apps less and less apps are installed you need to shine to be discovered user picks only best app among similar featured apps Hybrid Technologies Xamarin, Cordova, Flutter, Titanium, React Native, Flutter Be aware of the maturity lock-in effect infrastructure and tooling required might get worst of both world should be incrementable updatable check where it makes sense WebViews only Native App shells: Amazon App, Apple App Store, WeChat Mainly for smaller companies Trending on Google Links: AirBnB is sunsetting its React Native development What’s Next for Mobile at Airbnb Server-Driven Rendering Even though we’re not using React Native, we still see the val...