Android Market category strategy?

by Mark Carter » Fri, 27 Aug 2010 05:04:45 GMT

Sponsored Links
 I've just released an app which could feasibly go into any one of
three different categories: Reference, Travel, Communication.

Looking at this page: 

there are more apps in Reference, followed by Travel, then

Its probably a double-edged sword to place an app in a more popular

Or maybe occasionally switch the app between different categories?

I'm guessing most people find apps through search rather than browsing
through categories?

Any thoughts?


Android Market category strategy?

by Maps.Huge.Info (Maps API Guru) » Fri, 27 Aug 2010 05:59:48 GMT

 When you consider that most categories have "sexy wallpaper" (and
other spam apps) in them, the value of categories sort of lose some
luster. I suggest just picking one that you feel is most appropriate
and stick with it. Switching categories probably has no effect on your
popularity but it could cause some confusion among your users. When
you first start out, the only way a user will find your app is by
search so category doesn't mean much. Once you start moving up in the
popularity, category becomes more important but unless you're at least
in the top 800, it's really irrelevant.

The "Just in" tab in the category is also pretty much rendered moot as
the "sexy wallpaper" apps are updated so often that the "just in" tab
is always flooded with spam.

I say top 800 because the market stops listing apps after 800 have
been displayed. Perhaps that will change in the future.

-John Coryat


Sponsored Links

Android Market category strategy?

by TreKing » Fri, 27 Aug 2010 08:57:06 GMT


Probably, but I often peruse the top app in each category to see what's hot
that I'm missing out on, I'm sure others do as well.

Otherwise, I agree with John. But pick between Reference and Communication,
Travel is mine! =P

On Thu, Aug 26, 2010 at 4:59 PM, Maps.Huge.Info (Maps API Guru) <

Wait ... you scrolled through 800 apps ... and counted them?

TreKing <> ; - Chicago
transit tracking app for Android-powered devices


Android Market category strategy?

by Mark Carter » Fri, 27 Aug 2010 13:55:42 GMT

 Thanks guys.

The app is an SMS addon to an existing app I have in Reference (which
appears pretty high up in the list). I say addon, though it also works (with
reduced functionality) if the main app is not installed. I was thinking of
putting it in another category to try to expand my reach.

But I suppose, just sticking it in the same category as the main app will
cause less confusion.


Android Market category strategy?

by Nathan » Sat, 28 Aug 2010 01:53:09 GMT


I wouldn't mind having some more specific categories. My app isn't
really 'travel' but it is the closest I can get.

If they had some subcategories I would be out of TreKing's hair - not
that I'm a threat. I haven't managed to take down Google Maps in the
free category either ;).

My app could fit in Sports - but not really. And what app *doesn't*
fit in lifestyle or tools. But this matters not unless I'm in the top
N (where N << 800).

Ideally, I'd like to have a category so specific my app would be at
the top and possibly the only one in it. Yes, I'm dreaming.

Good job, John. Someone had to figure that out.

But I expect that an app falls into irrelevancy far sooner than 800
for the average user, whether they are counting or not. In,
few users go past the first page. Since the search in the Market is so
bad, I can guess users will go through several pages, but I know of no

There are some keyword searches where I come up somewhere between 20
and 800, yet people found my app, so there are some patient searchers
out there.

If the Market ever allows searching by category AND keyword, category
will become more important.



Android Market category strategy?

by niko20 » Tue, 31 Aug 2010 03:45:12 GMT

 I've scrolled all the way to the bottom of an apps list quite a few
times on the phone. Didn't know there were 800 though. But sometimes
I'll just scroll through everything to see if anything interesting
shows up. I'm sure I'm not the only one to do so.



Android Market category strategy?

by TreKing » Tue, 31 Aug 2010 04:48:58 GMT


I actually do as well, the Just In list in particular, because that's what
it takes to find something interesting amongst the sea of garbage. Never
thought to count though =P

TreKing <> ; - Chicago
transit tracking app for Android-powered devices


Other Threads

1. Socket connection using native socket() functions

I want to open a socket connection using native socket functions. I'm
able to bind the socket at the server side. But when i try to connect
to server from from a client, the connection is not being accepted at
server side. Accept() function is not bien called at server side.

Please somebody help me.

Related link:

2. SurfaceFlinger uses too much cpu


This is regarding SurfaceFlinger performance. If you think I have a
point here please let me know.

I have observed during my Camera application SurfaceFlinger consumes
too much of cpu (>80%).
Tried to know its cause, its found out that it is actually drawing the
lipregion twice consecutively. By drawing twice I mean, the
coordinates values are same for the 2 clip regions which gets drawn in
The lipregion is calculated from Layer visibleRegion and dirty
region. So in this case 2 layers in the currentstate are such that
they are calculating similar clip region.

I tried a hack not to draw the clip twice in
SurfaceFlinger::composeSurfaces() if it has same coordinates value,
before it calls layer->draw(clip) . It worked with no visible side
effects and cpu performance improved. That makes me think that it
might be a bug or scope of improvement in surfaceflinger.

Log showing 2 consecutive Layers calculating same region to draw:

E/SurfaceFlinger(  976): + LayerBuffer 0x3b3920
E/SurfaceFlinger(  976):       z=    21010
D/Region  (  976):   Region visibleRegionScreen (this=0x3b3930,
D/Region  (  976):     [ 32,  26, 208, 261]
D/Region  (  976):   Region clipDUMP (this=0x44fa19c4, count=1)
D/Region  (  976):     [ 32,  26, 208, 261]
E/SurfaceFlinger(  976): composeSurfaces layer->draw()
E/SurfaceFlinger(  976): + Layer 0x3e3110
E/SurfaceFlinger(  976):       z=    21015
D/Region  (  976):   Region visibleRegionScreen (this=0x3e3120,
D/Region  (  976):     [  0,   0, 240, 320]
D/Region  (  976):   Region clipDUMP (this=0x44fa19c4, count=1)
D/Region  (  976):     [ 32,  26, 208, 261]
E/SurfaceFlinger(  976): composeSurfaces layer->draw()

Any suggestions will be highly appreaciated..



3. User Mode Device Drivers

4. USB Android gadget

5. Possible to only kernel upgrade?

6. Activity pause timeout for HistoryRecord?

7. How to get Lat and Long about one bus line from google maps