Yes, those are the only two options: unique device ID or user account.
Problem is most users don't want to create user accounts for every app.
Device ID is more transparent to the user.

On Fri, Mar 23, 2012 at 3:21 PM, Shazron <[email protected]> wrote:

> Thanks Josh - that's what I've been warning people about in the Google
> Groups. We are just filling in functionality that we promised in the
> API for device.uuid going forward. Obviously the doc description for
> the property and expectations will change. Devs will have to adjust.
>
> On Fri, Mar 23, 2012 at 3:18 PM, Josh Marinacci <[email protected]>
> wrote:
> > Apple doesn't want you to have a way of uniquely permanently identifying
> a device. Any method you find to do this will eventually be closed.  It
> probably isn't what you want anyway. What are you really trying to track?
> The user or the device? For example, what happens if the user's phone is
> destroyed and they reinstall the app on a new device.  It's the same user
> and same app and same data, but a different device. Or what if they have
> two devices running the same app (iPhone and iPad).  Instead you should
> create and save some sort of unique identifier the first time the app is
> installed. Reference this to uniquely identify this *particular* install of
> the *app* on this *particular* device. If you need something that survives
> across app installs and devices then you should create a server based user
> account and let the user identify themselves upon reinstall (ex: Facebook,
> twitter, etc.)
> >
> > --
> > Josh Marinacci
> > joshondesign.com
> >
> >
> > On Friday, March 23, 2012 at 3:09 PM, Shazron wrote:
> >
> >> Actually - we could get the nic address on iOS through some BSD API
> >> (legitimately). Until Apple bans it of course - which I figure they
> >> would if people start using this as the UUID now - so the risk is high
> >> if we use the mac address.
> >>
> >> On Fri, Mar 23, 2012 at 1:35 PM, Jesse MacFadyen
> >> <[email protected] (mailto:[email protected])> wrote:
> >> > iPads and iPods don't have phone numbers and there is no API to get it
> >> > on iPhone.
> >> >
> >> > Same for nic and any other device specific value.
> >> >
> >> > Re: file path, is the guid per install, or is it really just a hash of
> >> > deviceId and appId? Does it survive app updates? resync's?
> >> >
> >> > File path is not a guid on WP7, in fact it is unknown. Sandboxed
> wpapp://
> >> >
> >> >
> >> >
> >> > Cheers,
> >> >  Jesse
> >> >
> >> > Sent from my iPhone5
> >> >
> >> > On 2012-03-23, at 1:23 PM, Bryce Curtis <[email protected](mailto:
> [email protected])> wrote:
> >> >
> >> > > Just an idea, but is there something else, like the phone number or
> MD5 of
> >> > > it, that could be used - so you don't have to gen one and then
> stash it
> >> > > around somewhere.
> >> > >
> >> > > On Fri, Mar 23, 2012 at 3:18 PM, Brian LeRoux <[email protected] (mailto:
> [email protected])> wrote:
> >> > >
> >> > > > like that idea shaz --- good symmetry
> >> > > >
> >> > > > really, the same could be said for all apps/platforms
> >> > > >
> >> > > > On Fri, Mar 23, 2012 at 12:56 PM, Shazron <[email protected](mailto:
> [email protected])> wrote:
> >> > > > > Here's an idea - since the app folder name is a GUID, we could
> just
> >> > > > > use that? This will only "break" if Apple decides to not use
> GUIDs for
> >> > > > > folder names.
> >> > > > >
> >> > > > > On Fri, Mar 23, 2012 at 11:50 AM, Shazron 
> >> > > > > <[email protected](mailto:
> [email protected])> wrote:
> >> > > > > > Yup - that is the only approach really. All the rest is
> implementation
> >> > > > > > details (keychain or iCloud or some doohickey)
> >> > > > > >
> >> > > > > > On Fri, Mar 23, 2012 at 11:44 AM, Filip Maj 
> >> > > > > > <[email protected](mailto:
> [email protected])> wrote:
> >> > > > > > > Sounds like the WP7/GUID approach is the best we can do for
> now. Back
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > > > that
> >> > > > > > > up with a new Quirk in the Device API documentation and I
> think that's
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > all
> >> > > > > > > we can do, really.
> >> > > > > > >
> >> > > > > > > On 3/23/12 11:42 AM, "Jesse MacFadyen" <
> [email protected] (mailto:[email protected])>
> >> > > > wrote:
> >> > > > > > >
> >> > > > > > > > WP7 generates a guid if the device I'd is not available.
> Guid is
> >> > > > > > > > persistent and is only generated on first run. This will
> not survive a
> >> > > > > > > > re-install of the app, but does identify a particular app
> >> > > > > > > > installation.
> >> > > > > > > >
> >> > > > > > > > Cheers,
> >> > > > > > > > Jesse
> >> > > > > > > >
> >> > > > > > > > Sent from my iPhone5
> >> > > > > > > >
> >> > > > > > > > On 2012-03-23, at 11:31 AM, Michael Brooks <
> [email protected] (mailto:[email protected])>
> >> > > > > > > > wrote:
> >> > > > > > > >
> >> > > > > > > > > Darn.
> >> > > > > > > > >
> >> > > > > > > > > Any idea what we should do about `device.uuid`? [1]
> It's a PhoneGap
> >> > > > > > > > > homebrewed API.
> >> > > > > > > > >
> >> > > > > > > > > [1]
> >> > > >
> http://docs.phonegap.com/en/1.5.0/phonegap_device_device.md.html#device.u
> >> > > > > > > > > uid
> >> > > > > > > > >
> >> > > > > > > > > On Fri, Mar 23, 2012 at 11:18 AM, Shazron <
> [email protected] (mailto:[email protected])> wrote:
> >> > > > > > > > >
> >> > > > > > > > > > According to
> >> > > > > > > > > >
> https://twitter.com/#!/TheKevinDent/status/182540197769134080
> >> > > > > > > > > > Prob because of the Path AddressBook fiasco. Will
> accelerate this:
> >> > > > > > > > > > https://issues.apache.org/jira/browse/CB-49
> >> > > > > > > > > >
> >> > > > > > > > > > Will get it into 1.6.0 since this is will be an big
> issue. Apple is
> >> > > > > > > > > > sure keeping me busy working around their policies /
> bugs these
> >> > > > > > > > > > days...
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >>
> >
> >
>

Reply via email to