I took a look at your sample report (http://usermetrix.com/projects/2) and your home page, and it looks like you have a combination of Java AOP logging and exception logging to a database, and then you make a report based on that? Is there anything "actionable" in the report?
So the people buying this service will be Java end-user app developers and their managers, no one else will really need it?
How about: "UserMetrix lets Java and Android developers measure feature adoption and exception message trends across applications to pinpoint usability and functional problems before your users notice"
Provides developers with a huge head start on narrowing down and pinpointing the root cause of a problem rather than just the symptom, NPE or whatever.
You should probably tie software versions (of the app being instrumented) into your tracking and reporting as well, so if errors are still being thrown, that's because the user's on 2.0 and the bug is fixed in 2.0.1
Comments
I think that's pretty vague.
I took a look at your sample report (http://usermetrix.com/projects/2) and your home page, and it looks like you have a combination of Java AOP logging and exception logging to a database, and then you make a report based on that? Is there anything "actionable" in the report?
So the people buying this service will be Java end-user app developers and their managers, no one else will really need it?
How about: "UserMetrix lets Java and Android developers measure feature adoption and exception message trends across applications to pinpoint usability and functional problems before your users notice"
Hey Jeff,
Thanks for taking the time to work that up - your value proposition is a huge improvement.
Currently Java end-user app developers and their managers is very much the target audience.
The biggest thing that is actionable in the report is the most likely reproduction steps - see http://usermetrix.com/log_messages/8805/error for an example.
Provides developers with a huge head start on narrowing down and pinpointing the root cause of a problem rather than just the symptom, NPE or whatever.
Great! Glad I could help!
You should probably tie software versions (of the app being instrumented) into your tracking and reporting as well, so if errors are still being thrown, that's because the user's on 2.0 and the bug is fixed in 2.0.1