AppUp Elements 2011 – Getting your app validated on AppUp

For any app store, getting your program validated can seem like a dark art – mysterious forces behind the scenes apparently there to halt your journey towards app success. Vipul Chopra at Intel has some tips on the validation process and what common traps to avoid to ensure your app makes it to the AppUp Center as quickly as possible.

The first thing to note is that there are two types of validation: binary and meta – in that order. Binary focuses on the app itself and meta focuses on the meta data you added as part of the submission process, including the app description etc.

The binary tests are as follows:
– Download, install, launch – your app should launch from the store and from a native location such as a desktop icon or program menu
– Primary functionality – buttons, features, menu items, levels, game play should all function correctly
– Check for viruses and malware – obviously, these should be absent
– An actual person will test and validate the app fully
– You can check guidelines on the Intel AppUp developer program website here

Meta validation test, which takes place after the binary validation, includes:
– A check on the content rating, which should be appropriate to the content of your app. Specific guidelines exist to help with this – for example, if the app accesses social media accounts such as Facebook or Twitter, it must be rated as 17+
– A check on the long and short descriptions you provided on your app -these should describe the content
– The validation team then assigns categories for your app to feature in (taking into account the suggestions you made during submission)
– If you have only changed the meta data since your last app submission, the binary validation is not needed and your app will be validated much faster

Common pitfalls to avoid:
– Apply for Microsoft code signing as soon as you join the program to avoid the five day wait that this entails when you want to submit your app
– Beta test your app on clean devices, not on development machine, and make sure you use basic factory settings
– Windows 7 starter has basic drivers, so apps cannot assume any resource is pre-installed
– Your app doesn’t launch from store due to relative path in the source code. Use the full path for application drivers and resource files. Beta testing will help to reveal this issue
– Creating MSI with bad shortcuts

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Get every new post delivered to your Inbox.

%d bloggers like this: