What would an intent URI look like for numeric data?

by Marco Nelissen » Fri, 06 Mar 2009 07:38:03 GMT

Sponsored Links
 Does it need to be in the data field? Normally you'd use
Intent.putExtra() for this.


What would an intent URI look like for numeric data?

by Dianne Hackborn » Sat, 07 Mar 2009 05:28:02 GMT

 There was a big reworking late in 1.0 of the result stuff that caused a lot
of things that used to be returning things as raw strings to put them in the
action field.  It is generally not something I would recommend.  And what
you do with results is very very different than what you do with activity
intents and such, because an activity intent is something you are publishing
to the system, which it does intent filter matching on, etc.

I would recommend putting things like integers in to the extra data.  I
would certainly not recommend using the data field if you don't actually
have a reasonable scheme prefix that is part of your data.

Dianne Hackborn
Android framework engineer

Note: please don't send private questions to me, as I don't have time to
provide private support.  All such questions should be posted on public
forums, where I and others can see and answer them.


Sponsored Links

Other Threads

1. Can't Upgrade Apps Since Console Maintenance ?

I understand the maintenance window is long past, but the Upload
Upgrade linky button just disappears when I click it for all my apps.

I can upload assets without problem e.g. the new 512x512 icon.

Anyone else ?



2. iOS UI Patterns Bleeding into Android apps

Twitter for Android is an excellent app, but the lastest update shows
how a lot of iOS UI patterns are bleeding over to Android apps,
potentially confusing things.

To note a couple:

1. Pull down ListView (beyond top) to refresh.
2. Swipe finger across a ListView row to bring up actions/edit.

First of all, iOS has some extremely well thought at and sensible UI/
UX patterns, many of them designed to get around the limitation of
having one physical button (always needing a back button on screen, no
menu key and so on).

The danger here is that as Android developers we don't have this stuff
built into the SDK, if you've tried to implement iOS's "overshoot"/
elastic ScrollViews which are purported to be coming to Gingerbread,
you'll know how much extra work this can be, and potentially how
brittle that might make code, especially if this particular feature is
going to be built in.

In response to the numbered points above, what about Android's "click
list view header to scroll to top", and what about the long-press for
bringing up actions/options for an item. TweetDeck is one of the best
examples of Android done right IMHO, fully embracing a lot of the
design and interaction guidelines that are beginning to emerge.

Are we going to confuse users by having an Android way to do things
mixed in with an iOS way to do things?


3. FM Recorder

4. Battrey life time

5. Tanya Skype for Android

6. Increase the Sampling Rate of Accelerometer

7. widget buttons/images changing the layout