OpenUDID can QuickConnect use this?

[Noli Sicad]

From the readme (below)

https://github.com/ylechelle/OpenUDID

Can QuickConnect use this?

Noli

################################################
Synopsis: an open source project to provide a universal and persistent
Unique Device IDentifier (UDID) solution for iOS and Android

Usage:
#include "OpenUDID.h"
NSString* openUDID = [OpenUDID value];

Needed:
- equivalent OpenUDID systems on Windows Mobile 7, Blackberry,
Windows .Net, etc...

Context:

If you’re not already familiar with UDID’s, it’s a critical tool for
analytic or CRM purposes. A developer could use UDID’s as a means to
track how much time a user spent in his free app before upgrading to
the paid version. UDID’s are also helpful for tracking the source of a
download when advertising on an ad network. This is a fairly universal
need in a thriving ecosystem: developers need the traceability from
clicks to downloads to ensure that they pay the right price for their
promotion. Proper tracking and funnel conversion is what has made the
web a better place, with healthy competition and quantifiable metrics.

In the wake of Apple’s decision, some ad networks have already
introduced their own proprietary solutions. The main motivation here
was to find a UDID replacement not owned by any single provider. It is
easy to foresee a fragmented market where UDID management is operated
by multiple providers with no cooperation between them. This open
source initiative is to enable a better solution for thousands of
other mobile app developers.

The agenda was as follows:
- Provide a reliable proxy and replacement for a universal unique
device identifier. That is, persistent and sufficiently unique, on a
per device basis.
- NOT use an obvious other sensitive unique identifier (like the MAC
address) to avoid further deprecation and to protect device-level
privacy concerns
- Enable OpenUDID to be accessed by any app
- Supply open-source code to generate and access the OpenUDID, for iOS
and Android
- Incorporate, from the beginning, a system that will enable user
opt-out to match Apple’s initial intent

History:
- August 2011: launch of the initiative
- Sept. 9 2011: v1.0 of the code meeting all requirements
- March. 25 2012: removing all traces of the offending call on iOS

[Aaron Madsen]

Noli,
I can't speak for Lee (and I have not done an thorough evaluation of
the code) but it definitely looks interesting. Even if it was not built
directly in to QuickConnect, we should be able to build it as a plugin
to Quickconnect Hybrid on both platforms to test it out. (Lee, please
remind me, did the plugin architecture get finished? I'm still using an
old code base.)

Aaron Madsen

On 3/26/12 6:17 PM, Noli Sicad wrote:
> From the readme (below)
>
> https://github.com/ylechelle/OpenUDID
>
> Can QuickConnect use this?
>
> Noli
>
> ################################################
> Synopsis: an open source project to provide a universal and persistent
> Unique Device IDentifier (UDID) solution for iOS and Android
>
> Usage:
> #include "OpenUDID.h"
> NSString* openUDID = [OpenUDID value];
>
> Needed:
> - equivalent OpenUDID systems on Windows Mobile 7, Blackberry,
> Windows .Net, etc...
>
> Context:
>

> If you�re not already familiar with UDID�s, it�s a critical tool for
> analytic or CRM purposes. A developer could use UDID�s as a means to

> track how much time a user spent in his free app before upgrading to

> the paid version. UDID�s are also helpful for tracking the source of a

> download when advertising on an ad network. This is a fairly universal
> need in a thriving ecosystem: developers need the traceability from
> clicks to downloads to ensure that they pay the right price for their
> promotion. Proper tracking and funnel conversion is what has made the
> web a better place, with healthy competition and quantifiable metrics.
>

> In the wake of Apple�s decision, some ad networks have already

> introduced their own proprietary solutions. The main motivation here
> was to find a UDID replacement not owned by any single provider. It is
> easy to foresee a fragmented market where UDID management is operated
> by multiple providers with no cooperation between them. This open
> source initiative is to enable a better solution for thousands of
> other mobile app developers.
>
> The agenda was as follows:
> - Provide a reliable proxy and replacement for a universal unique
> device identifier. That is, persistent and sufficiently unique, on a
> per device basis.
> - NOT use an obvious other sensitive unique identifier (like the MAC
> address) to avoid further deprecation and to protect device-level
> privacy concerns
> - Enable OpenUDID to be accessed by any app
> - Supply open-source code to generate and access the OpenUDID, for iOS
> and Android
> - Incorporate, from the beginning, a system that will enable user

> opt-out to match Apple�s initial intent

[Jeff Janes]

Hello all it has been a while since I posted anything but wanted to bring
this to all of your attentions

This link describes Apples possible action regarding the future use of
UDIDs.

http://www.appleinsider.com/articles/12/03/25/apple_begins_blanket_rejection
s_of_apps_that_access_udids.html

Just so no one does a lot of work and then has to make major modifications

Jeff

On 3/26/12 5:54 PM, "Aaron Madsen" <ama...@affinityamp.com> wrote:

> Noli,
> I can't speak for Lee (and I have not done an thorough evaluation of
> the code) but it definitely looks interesting. Even if it was not built
> directly in to QuickConnect, we should be able to build it as a plugin
> to Quickconnect Hybrid on both platforms to test it out. (Lee, please
> remind me, did the plugin architecture get finished? I'm still using an
> old code base.)
>
> Aaron Madsen
>
> On 3/26/12 6:17 PM, Noli Sicad wrote:
>> From the readme (below)
>>
>> https://github.com/ylechelle/OpenUDID
>>
>> Can QuickConnect use this?
>>
>> Noli
>>
>> ################################################
>> Synopsis: an open source project to provide a universal and persistent
>> Unique Device IDentifier (UDID) solution for iOS and Android
>>
>> Usage:
>> #include "OpenUDID.h"
>> NSString* openUDID = [OpenUDID value];
>>
>> Needed:
>> - equivalent OpenUDID systems on Windows Mobile 7, Blackberry,
>> Windows .Net, etc...
>>
>> Context:
>>

>> If you¹re not already familiar with UDID¹s, it¹s a critical tool for
>> analytic or CRM purposes. A developer could use UDID¹s as a means to

>> track how much time a user spent in his free app before upgrading to

>> the paid version. UDID¹s are also helpful for tracking the source of a

>> download when advertising on an ad network. This is a fairly universal
>> need in a thriving ecosystem: developers need the traceability from
>> clicks to downloads to ensure that they pay the right price for their
>> promotion. Proper tracking and funnel conversion is what has made the
>> web a better place, with healthy competition and quantifiable metrics.
>>

>> In the wake of Apple¹s decision, some ad networks have already

>> introduced their own proprietary solutions. The main motivation here
>> was to find a UDID replacement not owned by any single provider. It is
>> easy to foresee a fragmented market where UDID management is operated
>> by multiple providers with no cooperation between them. This open
>> source initiative is to enable a better solution for thousands of
>> other mobile app developers.
>>
>> The agenda was as follows:
>> - Provide a reliable proxy and replacement for a universal unique
>> device identifier. That is, persistent and sufficiently unique, on a
>> per device basis.
>> - NOT use an obvious other sensitive unique identifier (like the MAC
>> address) to avoid further deprecation and to protect device-level
>> privacy concerns
>> - Enable OpenUDID to be accessed by any app
>> - Supply open-source code to generate and access the OpenUDID, for iOS
>> and Android
>> - Incorporate, from the beginning, a system that will enable user

>> opt-out to match Apple¹s initial intent

[Noli Sicad]

"Apple reportedly rejecting apps that access UDIDs"

Do QuickConnect uses UDIDs?

For a simple app developer do really worry about this UDID's?

Noli

> --
> You received this message because you are subscribed to the Google Groups
> "QuickConnect" group.
> To post to this group, send email to quickconn...@googlegroups.com.
> To unsubscribe from this group, send email to
> quickconnectiPh...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/quickconnectiPhone?hl=en.
>
>

[Barney Cit]

Aaron,

The plugin functionality is complete in iOS but not yet Android.

Could this be used in QC? Yes but I don't see any major difference between this code and the UUID generator already existing in the JavaScript side of QC. In fact it is quite similar, though not exactly the same.

Lee

Sent from my iPad

On Mar 26, 2012, at 6:54 PM, Aaron Madsen <ama...@affinityamp.com> wrote:

> Noli,
> I can't speak for Lee (and I have not done an thorough evaluation of the code) but it definitely looks interesting. Even if it was not built directly in to QuickConnect, we should be able to build it as a plugin to Quickconnect Hybrid on both platforms to test it out. (Lee, please remind me, did the plugin architecture get finished? I'm still using an old code base.)
>
> Aaron Madsen
>
> On 3/26/12 6:17 PM, Noli Sicad wrote:
>> From the readme (below)
>>
>> https://github.com/ylechelle/OpenUDID
>>
>> Can QuickConnect use this?
>>
>> Noli
>>
>> ################################################
>> Synopsis: an open source project to provide a universal and persistent
>> Unique Device IDentifier (UDID) solution for iOS and Android
>>
>> Usage:
>> #include "OpenUDID.h"
>> NSString* openUDID = [OpenUDID value];
>>
>> Needed:
>> - equivalent OpenUDID systems on Windows Mobile 7, Blackberry,
>> Windows .Net, etc...
>>
>> Context:
>>

>> If you’re not already familiar with UDID’s, it’s a critical tool for
>> analytic or CRM purposes. A developer could use UDID’s as a means to

>> track how much time a user spent in his free app before upgrading to

>> the paid version. UDID’s are also helpful for tracking the source of a

>> download when advertising on an ad network. This is a fairly universal
>> need in a thriving ecosystem: developers need the traceability from
>> clicks to downloads to ensure that they pay the right price for their
>> promotion. Proper tracking and funnel conversion is what has made the
>> web a better place, with healthy competition and quantifiable metrics.
>>

>> In the wake of Apple’s decision, some ad networks have already

>> introduced their own proprietary solutions. The main motivation here
>> was to find a UDID replacement not owned by any single provider. It is
>> easy to foresee a fragmented market where UDID management is operated
>> by multiple providers with no cooperation between them. This open
>> source initiative is to enable a better solution for thousands of
>> other mobile app developers.
>>
>> The agenda was as follows:
>> - Provide a reliable proxy and replacement for a universal unique
>> device identifier. That is, persistent and sufficiently unique, on a
>> per device basis.
>> - NOT use an obvious other sensitive unique identifier (like the MAC
>> address) to avoid further deprecation and to protect device-level
>> privacy concerns
>> - Enable OpenUDID to be accessed by any app
>> - Supply open-source code to generate and access the OpenUDID, for iOS
>> and Android
>> - Incorporate, from the beginning, a system that will enable user

>> opt-out to match Apple’s initial intent

>>
>> History:
>> - August 2011: launch of the initiative
>> - Sept. 9 2011: v1.0 of the code meeting all requirements
>> - March. 25 2012: removing all traces of the offending call on iOS
>>
>

[Barney Cit]

QC has a getUUID method in the JavaScript that doesn't use the device ID. It is the device ID that is UDID. You could use the generated UUID by storing the value on initial startup and then sending it each time you are connecting to the server.

Lee

Sent from my iPad

[Aaron Madsen]

Lee,
This code uses a shared UIPasteboard on iOS so that it generates the
UDID for device one for all apps that use this code. It provides a more
generic replacement for the Device Identifier because it can be shared
between apps. It may not be critical, but it is potentially useful.
That's why I was thinking a plugin.

Aaron

>>>>> If you嚙緝e not already familiar with UDID嚙編, it嚙編 a critical tool for
>>>>> analytic or CRM purposes. A developer could use UDID嚙編 as a means to

>>>>> track how much time a user spent in his free app before upgrading to

>>>>> the paid version. UDID嚙編 are also helpful for tracking the source of a

>>>>> download when advertising on an ad network. This is a fairly universal
>>>>> need in a thriving ecosystem: developers need the traceability from
>>>>> clicks to downloads to ensure that they pay the right price for their
>>>>> promotion. Proper tracking and funnel conversion is what has made the
>>>>> web a better place, with healthy competition and quantifiable metrics.
>>>>>

>>>>> In the wake of Apple嚙編 decision, some ad networks have already

>>>>> introduced their own proprietary solutions. The main motivation here
>>>>> was to find a UDID replacement not owned by any single provider. It is
>>>>> easy to foresee a fragmented market where UDID management is operated
>>>>> by multiple providers with no cooperation between them. This open
>>>>> source initiative is to enable a better solution for thousands of
>>>>> other mobile app developers.
>>>>>
>>>>> The agenda was as follows:
>>>>> - Provide a reliable proxy and replacement for a universal unique
>>>>> device identifier. That is, persistent and sufficiently unique, on a
>>>>> per device basis.
>>>>> - NOT use an obvious other sensitive unique identifier (like the MAC
>>>>> address) to avoid further deprecation and to protect device-level
>>>>> privacy concerns
>>>>> - Enable OpenUDID to be accessed by any app
>>>>> - Supply open-source code to generate and access the OpenUDID, for iOS
>>>>> and Android
>>>>> - Incorporate, from the beginning, a system that will enable user

>>>>> opt-out to match Apple嚙編 initial intent

[lee barney]

Why would one UUID need to be shared between apps for any reason other than reporting if more than one app from the same developer had been installed and to accumulate that and other data from multiple applications under one unique key? That is what the UDID was being used for and why access to the UDID has been removed.

It seems to me that the current regulatory pressures would indicate that including this type of behavior in applications could yield exactly the same issues that are currently causing Apple to remove access to the UDID. Granted one difference does exist. Without the UDID it would be harder to spoof the device or clone it but that isn't generally what 'they' are worried about anyway.

It can be used as a plugin. I'm not real comfortable building this into QC because I can see having to remove it in the future due to user privacy issues that will be raised.

Lee

>>>>>> If youąre not already familiar with UDIDąs, itąs a critical tool for
>>>>>> analytic or CRM purposes. A developer could use UDIDąs as a means to

>>>>>> track how much time a user spent in his free app before upgrading to

>>>>>> the paid version. UDIDąs are also helpful for tracking the source of a

>>>>>> download when advertising on an ad network. This is a fairly universal
>>>>>> need in a thriving ecosystem: developers need the traceability from
>>>>>> clicks to downloads to ensure that they pay the right price for their
>>>>>> promotion. Proper tracking and funnel conversion is what has made the
>>>>>> web a better place, with healthy competition and quantifiable metrics.
>>>>>>

>>>>>> In the wake of Appleąs decision, some ad networks have already

>>>>>> introduced their own proprietary solutions. The main motivation here
>>>>>> was to find a UDID replacement not owned by any single provider. It is
>>>>>> easy to foresee a fragmented market where UDID management is operated
>>>>>> by multiple providers with no cooperation between them. This open
>>>>>> source initiative is to enable a better solution for thousands of
>>>>>> other mobile app developers.
>>>>>>
>>>>>> The agenda was as follows:
>>>>>> - Provide a reliable proxy and replacement for a universal unique
>>>>>> device identifier. That is, persistent and sufficiently unique, on a
>>>>>> per device basis.
>>>>>> - NOT use an obvious other sensitive unique identifier (like the MAC
>>>>>> address) to avoid further deprecation and to protect device-level
>>>>>> privacy concerns
>>>>>> - Enable OpenUDID to be accessed by any app
>>>>>> - Supply open-source code to generate and access the OpenUDID, for iOS
>>>>>> and Android
>>>>>> - Incorporate, from the beginning, a system that will enable user

>>>>>> opt-out to match Appleąs initial intent