Best Practices for Separate Testing Android Applications

Question

To test sections of web applications, various options are usually tested separately to maximize their performance using tools such as Google Website Optimizer. One of the most impressive examples could be Google and how the split tested dozens of shades of blue to find the right one.

When Android apps are being developed, are there any best practices for A / B testing or multivariate testing?

Answer 1

Came here, then continued the results and came across an elegant answer . (Vincent Cao May 12, 11)

private static final boolean isA = UUID.randomUUID().getLeastSignificantBits() % 2 == 0; 

public void onCreate(Bundle savedInstanceState){ 
   super.onCreate(savedInstanceState); 

   if(isA){ 
       setContentView(R.layout.mainA); 
       MyApp.getInstance().tracker().trackPageView("/AUser"); 
   }else{ 
       setContentView(R.layout.mainB); 
       MyApp.getInstance().tracker().trackPageView("/BUser"); 
   } 
   ... 
}

My only thought is to keep the choice so that every time I return to the same layout.

Answer 2

I just looked at it (from here google search that brought me here). My search did not give in to the scope.

If you know, before running what you would like to test, it is quite simple (theoretically). Get started at home with your home phone and ask if the app should show A or B (and send on either side of the user when you submit the results).

, , . , . , , , :

http://developer.android.com/reference/dalvik/system/DexFile.html http://developer.android.com/reference/dalvik/system/DexClassLoader.html

, , . , , dex, , , .

. , , .

Answer 3

The best workaround would be to create a mobile application accessible through a mobile web browser. Thus, you can implement the a / b resource as optimized or something else. You are losing the benefits of having your own application. If you are trying to use your own application for testing, like on the Internet. I'm sorry you're out of luck, well, at least as far as I know.