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

Post a Comment

Most Favorite Posts

Judo App - Server Driven UI out of the box

Judo App Judo brings server-driven UI to your iOS and Android apps. Build user interfaces visually in a fraction of time and publish them instantly without submitting to the app store. Build Experiences - With No Code The Judo app for macOS, available through the App Store, is built for design professionals with common keyboard shortcuts and familiar concepts like canvas, layers and inspector panel. Workflow is streamlined with the ability to drag and drop media files directly into your experiences and manage your own Judo files in Finder. Manage Creative Execution A Judo experience is interactive and can include text, images, video and buttons. An experience may be part of a screen, a single screen, or more typically multiple linked screens. Judo supports screen transitions, carousels, horizontal scrolling and modals. Clients can add custom fonts and define global colors and these are updates applied universally. Effortlessly Deploy Judo Cloud syncs your experiences with your iOS and ...
Post a Comment
Read more

Dark Theme (Dark Mode) in Android WebViews, WKWebViews and CSS

So your apps just implemented a shiny new dark theme and it’s looking 👌 There are lots of benefits to having a dark theme in your application, and having it consistent throughout your application allows for a great user experience. But what happens when the the user runs into a WebView in your app? Support: if (WebViewFeature.isFeatureSupported(WebViewFeature.FORCE_DARK)) { ... } Set: WebSettingsCompat.setForceDark(webView.settings, WebSettingsCompat.FORCE_DARK_ON) Current setting: val forceDarkMode = WebSettingsCompat.getForceDark(webView.settings) Joe Birch Assuming your question is asking how to change the colors of the HTML content you are displaying in a WKWebView based on whether light or dark mode is in effect, there is nothing you do in your app's code. All changes need to be in the CSS being used by your HTML content. CSS dark mode via :root variables, explicit colors and @media query: :root {     color-scheme: light dark;      ...
Post a Comment
Read more

Server-driven UI (SDUI): Meet Zalandos AppCraft and AirBnB Lona

A short WTF: Joe Birch:  SERVER DRIVEN UI, PART 1: THE CONCEPT Zalando seems to follow the SDUI principle as well - defining a common design language and construct the screens on the backend while displaying them natively on the clients. They even go one step further; they implemented a mighty toolset to enable non-technical stakeholders to define their own native app screens Compass: Web tooling to create screens and bind data Beetroot: Backend service that combines the screen layout definition with the data Lapis/Golem: iOS/Android UI render engines Crazy cool! Good job, guys (when you do an open-source release?) To even move faster a Flutter based UI render engine implementation was great! See also AirBnB Lona SDUI approach Building a Visual Language Why Dropbox sunsetted its universal C++ mobile project and AirBnB its React Native implementation
2 comments
Read more

Remote Debugging WebViews with Android 4.4 KitKat

Starting Android 4.4 (KitKat), you can use the DevTools to debug the contents of Android WebViews inside native Android applications. Debugging WebViews requires: An Android device or emulator running Android 4.4 or later, with USB debugging enabled as described in 2. Enable USB debugging on your device . Chrome 30 or later. Enhanced WebView debugging UI is available in Chrome 31 or later. An Android application with a WebView configured for debugging. Android Developer
Post a Comment
Read more

PeekPop - Pre-iPhone 6S and 6S+

Peek and Pop Let your users preview all kinds of content and even act on it — without having to actually open it. Users can then press a little deeper to Pop into content in your app. Apple 3D Touch PeekPop Peek and Pop is a great new iOS feature introduced with iPhone 6S and 6S+ that allows you to easily preview content using 3D touch. Sadly, almost 80% of iOS users are on older devices. PeekPop is a Swift framework that brings backwards-compatibility to Peek and Pop. GitHub
Post a Comment
Read more

Android with Kotlin, iOS with Swift, Kotlin Native, flutter.io, React Native, PWA, Xamarin, Hybrid - which way to go?

Currently there are tons of frameworks how to get your business model to the user... and in the app store Full Native Android with Kotlin, iOS with Swift Deepest integration Single way to make sure that you have no lock-in effect with a framework, and you are f**ed, when Apple or Google disallows the usage of a specific technology... Two teams required 2x code PWA (Progressive Web App) Write offline- and push-capable PWA with web-technologies only Some native features might require hybrid native development and bridging (like In-App purchases, AR, ...) In best case: One web team only for website and app Maybe some native specialists for special features Kotlin Native Develop a shared framework with or without UI using Kotlin Native Additional native code will most probably be required Big Android team, small iOS specialists flutter.io (React Native | Xamarin | ... ) One codebase (flutter: Dart, React Native: JavaScript, Xamarin: C#) Additional native code ...
Post a Comment
Read more