Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
App storeaccreditationVersion 2 June 2011                      A global initiative of                                  Del...
1. Introduction1.1     Objectives of this documentIf you wish to sell your application via the various Movistar and O2 App...
2. The application tests2.1.1.1   InstallationWe will verify that your application correctly installs on the intended devi...
2.1.1.3    Correct categorisation of your applicationTo ensure your application is published into the correct category of ...
2.1.1.5    Antivirus scanThis test will scan for the presence of virus and malwares inside yourapplication. It is a condit...
2.1.1.7   Network ImpactTo	verify	the	impact	on	the	network	by	an	application,	we	will	executetwo tests:•	 	 se	the	applic...
2.1.1.8   User Authorisation for charging eventsWe will verify that your application         Other chargeable eventsinform...
2.1.1.9   Graceful state transitionYour application must allow the user to pause and reactivate manuallywithout a negative...
2.1.1.10 Compatibility (when application is executed) with SMS serviceWhere applicable we will verify that sending and rec...
2.1.1.14 Compatibility (when application is executed) with WEB serviceWhere applicable we will verify that using the Web b...
2.1.1.18 Compatibility (when application is executed) with voice callsWhere	applicable	we	will	verify	that	making	and	rece...
3 Device GroupingYour application will be tested against a “family” of similar devices, meaningwhen	you	upload	your	applic...
3 Device Grouping Platform              DevicesSamsung	keyboard       Samsung-S3550;	Samsung-GT-S3500	/                   ...
3 Device Grouping Platform              DevicesSony	Ericsson	JP-8     Sony	Ericsson-K850x;	Sony	Ericsson-W910i;	          ...
3 Device Grouping Platform              DevicesWindows Mobile Large   HTC	-HD2;	HTC-Touch	HD	T8282;	                      ...
3 Device Grouping Platform          DevicesBlackBerry	large   RIM-BB	9000	Bold;	RIM-BB	8900	Curve;	                   RIM-...
4 Testing FeesEach	application	submission	will	cost	25	euros	regardless	of	the	number	of	Movistar	and	O2	App	Store’s	you	p...
5 ReportingFor	each	submission	you	will	be	sent	an	email	confirming	the	result	of	the	certification	process.	If	positive	y...
6 TurnaroundIt	goes	without	saying	we	aim	to	test	your	application	as	quickly	as	possible,	but our service level agreement...
7 FeedbackIf	you	have	any	questions	or	suggestions	on	how	we	can	improve	our	accreditation	process,	please	check	out	the	F...
Upcoming SlideShare
Loading in …5
×

BlueVia App Store Accreditation Guide

2,251 views

Published on

If you would like to use BlueVia to publish your app into the Telefonica App Stores to reach millions of potential customers, read this guide to learn more about our process and tests.

Note if you wish to just plug in the BlueVia API's to enjoy enhanced features and new revenue opportunities but distribute your app independently of Telefonica, then these tests do not apply to you.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

BlueVia App Store Accreditation Guide

  1. 1. App storeaccreditationVersion 2 June 2011 A global initiative of Delivered by
  2. 2. 1. Introduction1.1 Objectives of this documentIf you wish to sell your application via the various Movistar and O2 App Storesyour application will need to pass the BlueVia App Store accreditation process.This document describes that process and the tests that will be conducted onyour application.The BlueVia App Store Accreditation process is provided by our partner Sogeti. Hint: If you wish to just plug in the BlueVia API’s and distribute your application independently of Telefonica then this accreditation policy will not apply to you.
  3. 3. 2. The application tests2.1.1.1 InstallationWe will verify that your application correctly installs on the intended device.Tests covered in this step include:• he required files and resources are successfully copied to the device T memory (or to removable memory as appropriate)• he device displays a message indicating that the installation has ended T successfully.• shortcut is created and no errors appear when the application is launched. A Hint: The Installation test is an entry level criteria test, meaning if one of these installation tests fails then your application will be rejected, and no additional testing will be conducted.2.1.1.2 BlueVia terms & conditions and content guideline complianceWe will verify that your application complies with the BlueVia Terms &Conditions and that the content of your application conform to the BlueViacontent guidelines.To do this, we will use the same documents that are published onBlueVia.com:• ttp://bluevia.com/en/page/view/nodepath/boilerplate.TermsAndConds h• http://bluevia.com/en/knowledge/getStarted.App-Stores-Content-PolicyUsing the Launch to store form on Bluevia.com you must also ensure youinclude your contact information, application metadata, price, and the AppStores you wish to submit the application into.We will check that the application complies with the terms and conditions and content policy for each country you wish to publish into. Hint: The terms & conditions & policy test is an entry level criteria test, meaning if one of these tests fails then your application will be rejected, and no additional testing will be conducted.
  4. 4. 2.1.1.3 Correct categorisation of your applicationTo ensure your application is published into the correct category of thevarious Movistar and O2 App Stores, we will check that your application matches the application categorisation option(s) you selected during thesubmission process. Hint: If your application fails the categorisation test we will send you a report detailing the failure and will re-categorise metadata of your application on your behalf. Failure of this test will not result in the rejection of your submission.2.1.1.4 Correct LocalisationYour application must support the primary regional language of the store youwish to publish into or English as appropriate.If your application is multi-lingual we will verify that the application offers the option to switch to the primary regional language, or includes English. Region Primary languages Spain Spanish Argentina Spanish or English Germany German or EnglishThe application will fail the localisation test if the mandatory language foreach region is not supported and selectable.
  5. 5. 2.1.1.5 Antivirus scanThis test will scan for the presence of virus and malwares inside yourapplication. It is a condition of the BlueVia terms and conditions that youdeliver applications free of virus and malware. Hint: If your application fails the antivirus test your application will be rejected. Telefonica reserves the right to take action against any breaches in the service terms and conditions.2.1.1.6 Network configuration persistenceWe will verify that the installation process does not modify the device’sexisting network configuration.Tests covered in this step include the post install verification of the following configuration settings:• APN• DNS• SIP• Proxy• Connection User / passwordThe application will fail the network configuration test if any modifications are made to the existing device configurations.
  6. 6. 2.1.1.7 Network ImpactTo verify the impact on the network by an application, we will executetwo tests:• se the application to generate traffic. We will verify that the generated U traffic is directly related to the user activity. • onitor the network traffic generated by the application over 1 hour of M constant usage.These tests are designed to identify coding errors in the application like a TCP connection opening without posterior closing, which could have anunforeseen impact on the network and /or create the potential of bill shock for the end user.The application will fail the network impact tests if:• he application attempts to open connections in the same context more T than 3 times per minute• The application opens more than 3 TCP connections simultaneously. Hint: You can read tips on how to write apps for the mobile network environment here: http://bluevia.com/en/knowledge/ getStarted.TechnicalGoodPractices
  7. 7. 2.1.1.8 User Authorisation for charging eventsWe will verify that your application Other chargeable eventsinforms the end user of events that We shall also verify that:produce charges to the their Movistaror O2 bill, and that the user is correctly • If your application generates SMS, asked to give their authorisation for the MMS, or voice / video calls outside of charge at the appropriate time. the provided BlueVia API’s then the user must always be informed beforeBlueVia API usage initiation.If your application uses one or more • If your application can generate SMS, of the charge generating BlueVia MMS, or voice / video calls outside of APIs, we will verify that the application the provided BlueVia API’s we will verifysuccessfully launches the BlueVia that it does not generate:Connect process at the appropriate time(like the initial launch of the application), - More than 100 SMS in 10 minutesand asks the user to authorise the - More than 50 MMS in 10 minutesapplication to use the BlueVia APIs ontheir behalf. - ore than 5 voice / Video calls in 10 M minutesThe application with fail theauthorisation tests if: The application will fail the user authorisation tests if:• The application does not successfully launch the BlueVia Connect process • If the application does not warn the user of premium service usage• If the application does not successfully complete the BlueVia • If the application exceeds the Connect process aforementioned limits. Hint: further information on BlueVia API authentication can be found here: http://bluevia.com/en/knowledge/getStarted. Authentication
  8. 8. 2.1.1.9 Graceful state transitionYour application must allow the user to pause and reactivate manuallywithout a negative experience.Tests covered in this step include:1. The application is running2. he application is switched to background mode T3. The connection manager is invoked4. The connection is closed from within the connection manager5. he application is switched in foreground T6. he application is switched back to background T7. The connection is open from within the connection manager8. The application is switched in foregroundThe application will fail the graceful state transition test if any errormessages are encountered.
  9. 9. 2.1.1.10 Compatibility (when application is executed) with SMS serviceWhere applicable we will verify that sending and receiving SMS is possibleduring the execution of your application.The application will fail the SMS compatibility test if sending or receiving anSMS effects the execution of your application.2.1.1.11 Compatibility (when application is paused) with SMS serviceWhere applicable we will verify that sending and receiving SMS is possiblewhilst your application is paused.The application will fail the SMS compatibility test if sending or receiving anSMS effects the execution of your application.2.1.1.12 Compatibility (when application is executed) with MMS serviceWhere applicable we will verify that sending and receiving MMS is possibleduring the execution of your application.The application will fail the MMS compatibility test if sending or receiving anMMS effects the execution of your application.2.1.1.13 Compatibility (when application is paused) with MMS serviceWhere applicable we will verify that sending and receiving MMS is possiblewhilst your application is paused.The application will fail the MMS compatibility test if sending or receiving anMMS effects the execution of your application.
  10. 10. 2.1.1.14 Compatibility (when application is executed) with WEB serviceWhere applicable we will verify that using the Web browser is possible duringthe execution of your application.The application will fail the web service compatibility test if using the Webbrowser effects the execution of your application.2.1.1.15 Compatibility (when application is paused) with WEB serviceWhere applicable we will verify that using the Web browser is possible whilstyour application is paused.The application will fail the web service compatibility test if using the Webbrowser effects the execution of your application.2.1.1.16 Compatibility (when application is executed) with WAP serviceWhere applicable we will verify that using the WAP browser is possible duringthe execution of your application.The application will fail the WAP service compatibility test if using the WAPbrowser effects the execution of your application.2.1.1.17 Compatibility (when application is paused) with WAP serviceWhere applicable we will verify that using the WAP browser is possible whilstyour application is paused.The application will fail the WAP service compatibility test if using the WAPbrowser effects the execution of your application.
  11. 11. 2.1.1.18 Compatibility (when application is executed) with voice callsWhere applicable we will verify that making and receiving calls is possible during the execution of your application.The application will fail the voice call service compatibility test if making and receiving calls effects the execution of your application.2.1.1.19 Compatibility (when application is paused) with voice callsWhere applicable we will verify that making and receiving calls is possible whilst your application is paused.The application will fail the voice call service compatibility test if making and receiving calls effects the execution of your application.2.1.1.20 Compatibility (when application is executed) with video call serviceWhere applicable we will verify that making and receiving video calls is possible during the execution of your application.The application will fail the video call service compatibility test if making and receiving video calls effects the execution of your application.2.1.1.21 Compatibility (when application is paused) with video call serviceWhere applicable we will verify that making and receiving video calls is possible whilst your application is paused.The application will fail the video call service compatibility test if making and receiving video calls effects the execution of your application.
  12. 12. 3 Device GroupingYour application will be tested against a “family” of similar devices, meaningwhen you upload your application we will test that it works against all of the devices in that category.As you may know the mobile environment is fragmented, so this approach is designed to save you money as you do not have to make multiple submissions for each individual handset type. We have grouped devicessupported in the Movistar and O2 App Stores, taking into account common features to ensure compatibility.Please take a look at the available groupings on pages 13-16 and check out the devices included in them.
  13. 13. 3 Device Grouping Platform DevicesSamsung keyboard Samsung-S3550; Samsung-GT-S3500 / GT-3500; Samsung-SGH-A706; Samsung- SGH-D800; Samsung-SGH-D820; Samsung-SGH-D836; Samsung-SGH-D900; Samsung-SGH-G600; Samsung-SGH-G800; Samsung-SGH-U600; Samsung-SGH-U800; Samsung-SGH-U900; Samsung-T809Sony Ericsson JP-7 Sony Ericsson-K800i; Sony Ericsson-K810x; Sony Ericsson-S500x; Sony Ericsson- W850x; Sony Ericsson-K770x; Sony Ericsson-K790; Sony Ericsson-K800i; Sony Ericsson-S500; Sony Ericsson-T650x; Sony Ericsson-W580x; Sony Ericsson-W880xNokia S60 3rd FP2 Nokia-E75; Nokia-6220 classic; Nokia-N78; Nokia-N79; Nokia- N85 (3G); Nokia-N96; Nokia-5320; Nokia-5630 Xpress Music; Nokia-6210 Navigator; Nokia-6700; Nokia-6710 Navigator; Nokia-N78; Nokia-N86Nokia S60 3rd FP1 Nokia-N95; Nokia-5700 XpressMusic; Nokia- 6120 classic; Nokia-5700; Nokia-6110 Navigator; Nokia-E51; Nokia-E66; Nokia-N81; Nokia-N95 8GBSony Ericsson JP 8.3 Sony Ericsson-C702x; Sony Ericsson- W980x; Sony Ericsson-C902x; Sony Ericsson-W595x; Sony Ericsson-W760i; Sony Ericsson-Z780Nokia S40 5th Nokia-6600 slide; Nokia-7610 Supernova; Nokia-2700 classic; Nokia-5130; Nokia-5220 Xpressmusic; Nokia-5310 XpressMusic; Nokia-5610; Nokia-6500 classic; Nokia-6500 slide; Nokia-6600 Slide; Nokia-6600i slide
  14. 14. 3 Device Grouping Platform DevicesSony Ericsson JP-8 Sony Ericsson-K850x; Sony Ericsson-W910i; Sony Ericsson-Z750i; Sony Ericsson-W890x; Sony Ericsson-W995Nokia S40 3rd Nokia-6300; Nokia-6233; Nokia-6131; Nokia-6300Nokia S60 5th Nokia-N97 mini; Nokia-N97; Nokia-5800 XpressMusic; Nokia-5530 XpressMusic; Nokia-5230 Xpressmusic; Nokia-X6; Nokia-C6Samsung keyboard Samsung-E496; Samsung-E570; Samsung-E576; Samsung-E740; Samsung-J800; Samsung-S3100; Samsung-SGH-A736; Samsung-SGH-A767; Samsung-SGH-D500; Samsung-SGH-E380; Samsung-SGH-L700; Samsung-SGH-L760; Samsung-T459; Samsung-X576; Samsung-Z170; Samsung-Z240Sony Ericsson JP-8.4 Sony Ericsson-C510x; Sony Ericsson- W508x; Sony Ericsson-C905x; Sony Ericsson-W705Sony Ericsson JP-7 Sony Ericsson-K610i; Sony Ericsson-K550x; Sony Ericsson-K530i; Sony Ericsson-K610i; Sony Ericsson-W710; Sony Ericsson-Z710Samsung Touch Screen Samsung-S3650; Samsung-SGH- F480i; Samsung-B5310 Corby Qwerty; Samsung-F400; Samsung-S5600; Samsung-G400; Samsung-GT-S5620; Samsung-S8000 (Jet); Samsung-S5230Sony Ericsson JP-6 Sony Ericsson-W810x; Sony Ericsson- W550i; Sony Ericsson-W600; Sony Ericsson-W302
  15. 15. 3 Device Grouping Platform DevicesWindows Mobile Large HTC -HD2; HTC-Touch HD T8282; HTC-Touch Pro 2; O2-XDA Touch HD; Samsung-i8000 (Omnia II); Sony Ericsson- Xperia X2; Toshiba -TG02; Toshiba-TG01; Xda-Diamond 2Windows Mobile small HTC-Mega; HTC-P3451; HTC-P4351; HTC-TOUCH CRUISE; HTC-TYTN2; Motorola-Q9; O2-XDA Orbit; Samsung- GT-C6620; Samsung-I617; Samsung-i900 Omnia; Xda-GuideAndroid 1 HTC-Android Generic; HTC-G1 Dream (Alternative UA); HTC-G1 Dream; HTC-G2 Magic (Alternative UA2); HTC-G2 Magic (Alternative UA); HTC-Hero; HTC-G2 Magic; HTC-Tattoo (Alternative UA); HTC-Tattoo; Huawei-U8110; Huawei-U8230; LG-GT540; LG-GW620 (Alternative UA); LG-GW620; Motorola-MB220; Samsung-GT-I5700; Samsung-GT-I7500 (Galaxy) (Alternative UA); Samsung-GT-I7500; SonyEricsson- Xperia X10 (Alternative UA); SonyEricsson- XPERIA X10 mini; SonyEricsson-XPERIA X10 mini pro; SonyEriccson-XPERIA X8Android 2 HP-Compaq AirLife 100; HTC-Desire (Bravo) (Alternative UA); HTC-Desire (Bravo); HTC- Desire HD; LG-P350 (Pecan); LG-P990 (Optimus 2X); Motorola-MB220 Client; Motorola-MILESTONE; Samsung-GT-I9000 (Galaxy S); Samsung-GT-I9003 Galaxy SL; Samsung-GT-S7070; SonyEricsson-XPERIA Arc; SonyEricsson-R800; SonyEricsson- Xperia X10 (Safari Browser)
  16. 16. 3 Device Grouping Platform DevicesBlackBerry large RIM-BB 9000 Bold; RIM-BB 8900 Curve; RIM-BB 9700 Onyx; RIM-BB 9300; RIM-BB 8520BlackBerry small RIM-BB 8100 Pearl; RIM-BB 7230; RIM-BB 7100; RIM-BB 8110; RIM-BB 7130; RIM-BB 8120
  17. 17. 4 Testing FeesEach application submission will cost 25 euros regardless of the number of Movistar and O2 App Store’s you publish into. Please take into account that this fee only covers one submission to the process. If your application doesnot pass the accreditation you will have to fix the issues highlighted, resubmit and pay a second accreditation fee.
  18. 18. 5 ReportingFor each submission you will be sent an email confirming the result of the certification process. If positive your app will be placed on sale in your chosen Telefonica App Store(s). If negative you will receive a full reporthighlighting the issues that caused the failure in certification.
  19. 19. 6 TurnaroundIt goes without saying we aim to test your application as quickly as possible, but our service level agreement with you is to complete accreditation within5 working days.
  20. 20. 7 FeedbackIf you have any questions or suggestions on how we can improve our accreditation process, please check out the FAQ’s on BlueVia.com or contactsupport@bluevia.com.

×