Yo again,
A few clarifying comments to Yahel:
Yahel wrote:
There is no way anyone is going to actually browse more than a few
hundred item in a list. Ever !!
I guess it depends what the items are, but in my particular tree 95% of
the lists are quite short and being sortabel should help a lot to get
the particular PART of the list you are after.
Jim is right : Search & Pagination.
In my case, that was already there. A nice side effect is that it is now
easy to get a list of other products in the same category.
If your users are dumb enough to asks the full list and you are
actually going to do it, then implements a list like the android
market and fetch a 100 items at a time.
Done done. (T-50 days)
I'm pretty sure if you use Flurry to check what your users are doing.
You'll find only one or two users sliding below 200 items.
No need for Flurry&CO - it is trivial to see in the web service log.
And a user that asks you to get 30 000 items, is probably a
competitor that just wants to steal your database through your
webservice anyway :D
Nah, 30000 was just the extreme case. The data is freely available
anyway and it is continously updated, so stealing it is hardly an issue.
The point of my app is to make is easily accessible on the phone (well,
along with using GPS and barcode scanning etc to make it even more
powerful).
Best / Jonas
--
You received this message because you are subscribed to the Google
Groups "Android Developers" 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-developers?hl=en
To unsubscribe from this group, send email to
android-developers+unsubscribegooglegroups.com or reply to this email with the words
"REMOVE ME" as the subject.
