Topics In Demand
Notification
New

No notification found.

Blog
Measuring which features 'stick'? or 'A/B' testing for features within application

February 7, 2015

587

0


Listen to this article



Hi, I’ve been developing web applications from a long time now, some are huge success and some are bust. But I’ve never thought of successful applications as having made several right decisions and few wrong ones, and vice-versa. So from last few weeks I’m exploring the new ideas of measuring what makes an application success. Is it possible to increase odds of success if we make continuous right decisions based on data? like:

  • which interface version is better, a or b?
  • is ‘feature 1’ used and liked by more people when ‘interface 1’ is used, and not with ‘interface 2’? etc.

Of course at the end of day a lot would depend on your sales and marketing, but I’m only pointing out to increase the application’s stick-ability to the end users.

I want to explore, if anyone’s had a success story with such kind of system? Has anyone thought about trying it? What are the challenges of putting such system in place? Disadvantages? Is it worth? too complex? impossible?

Whatever you have to say about it – please share.


That the contents of third-party articles/blogs published here on the website, and the interpretation of all information in the article/blogs such as data, maps, numbers, opinions etc. displayed in the article/blogs and views or the opinions expressed within the content are solely of the author's; and do not reflect the opinions and beliefs of NASSCOM or its affiliates in any manner. NASSCOM does not take any liability w.r.t. content in any manner and will not be liable in any manner whatsoever for any kind of liability arising out of any act, error or omission. The contents of third-party article/blogs published, are provided solely as convenience; and the presence of these articles/blogs should not, under any circumstances, be considered as an endorsement of the contents by NASSCOM in any manner; and if you chose to access these articles/blogs , you do so at your own risk.


© Copyright nasscom. All Rights Reserved.