On 06/25/2010 08:38 PM, TreKing wrote: > On Fri, Jun 25, 2010 at 12:07 PM, Olivier Guilyardi <[email protected] > <mailto:[email protected]>> wrote: > > 1. it would be very logical, because it implies badly maintained > apps, where the > developer do not take (little) time to come and check the new errors. > > That's not logical - how, exactly, would the developer console know that > you actually fixed the reported bugs? Also, lots of bugs does > not necessarily mean the app is badly maintained. All apps have bugs, > but a popular app with hundreds of thousands of users will very likely > have many more bug reports by sheer volume than an app with a smaller > install base. This does not mean that second app is any better maintained.
I think there's some logic in what I said, but there's some logic in what you are saying too :) I was thinking that it could be a parameter of the whole rank algorithm, which would get superseded by such parameters as very big user base, etc... The console doesn't know if the bugs are really fixed, but someone not caring to check and mark bugs as old is likely not to be monitoring his apps. Also, if bugs aren't fixed, they'll come up again. > Also, in some other bug trackers that I know, it is not only the > number of errors which affect rank, but also how old they are. And > in my case, it's starting to get older and older. > > > What makes you think the Android Console bug tracker works this way? It's just an assumption from my experience of having worked with many of trackers and other open source projects. For instance, at PEAR, "Package Maintenace Rank" is computed in a similar way. Ohloh analyzes svn commits, number of devs, etc.. No bug tracking here, but if that was possible it might. > 3. the dates at which the rank-lost and this console problem started > to occur > really seem to match. > > > It's called coincidence. It's also called "the Android Market is > completely unpredictable and prone to temper tantrums, where app > rankings shift dramatically, download counts are lost, and apps can no > longer be found at all". Welcome to the "Google Experience"! I follow you here. I guess the tantra thing is very probable ;) I suppose one good answer to this is to mainly consider the market as a distribution channel, and rely on other means for promotions (twitter, whatever..) > I can't be sure, that's right, but I'd really like this console bug > to get fixed to make it clearer. > > This would be nice and will probably happen eventually. Remember this > bug tracking thing is still very new and definitely reeks of "beta". Yep, truly beta AFAICS, and using it for rank computation would be quite unacceptable at this stage. But since I already had a taste of the "Google Experience", I though it might... -- Olivier -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
