Our payload class stores the it's contents in NSDictionary *payload. Inheriting from NSDictionary would be cleaner as well as storing in the object itself rather than a property within the object.

Some place to keep all the string constants we have lying around in different classes into some organized fashion.

Resources:

• http://stackoverflow.com/questions/5287636/json-schema-to-objective-c-model-classes-generation
• http://jsonpack.com/ModelGenerators/ObjectiveC - doesn't seem to be working
• https://github.com/BrunoAlexandreMendesMartins/CleverModels
• https://github.com/icanzilb/JSONModel
• http://www.wope-framework.com/fr/blog/streamlining-objective-c-business-objects-parsing-using-json-schema/
• https://code.google.com/p/bkjsonschema/

Any mobile-specific contextual information we can get.

So far we have:

{
  "osType":"ios",
  "osVersion":"6.1"
}

See here for full list of ideas:

See also:

• snowplow/snowplow#744
• #7
• #19

https://github.com/segmentio/analytics-ios/tree/master/Analytics/Helpers

This is an idea to make timestamps more accurate.

The problem on mobile:

1. Device clocks and thus dvce_timestamp can be unreliable
2. collector timestamp can be out by days (due to delayed send)

The proposed solution:

1. When we send an event, we record the delta in ms between a) when the event was generated on the device and b) when it was sent. This delta is calculated using exclusively the device clock. If an event fails to send, then obviously the delta is recalculated for the next send
2. When we process an event in the Enrichment, we create a new timestamp, collector_tstamp_adjusted, which is the collector_tstamp minus the delta recorded in 1

So we end up with a new timestamp which is anchored by the collector_tstamp, but is adjusted to take account of delayed send.

This is only useful/important for trackers which have a lot of delayed send.

/cc @yalisassoon, @jonalmeida for thoughts. Unscheduled

NSLog is meant for logging errors, but it’s convenient to use it for debugging. We need to remove it so we don’t spam the error logs or give off sensitive information in them.

Possible solutions:

• Enable and Disable NSLog in DEBUG mode
• Dropping NSLog in release builds
• You're Doing It Wrong #1: NSLog("Debug");

It's not easily possible to build against the iOS 6.1 SDK with XCode 5 (Apple enforces you to build for 7+), so a workaround like this would be needed.

Note: Currently building against 7.1

See JavaScript Tracker for approach (and/or talk to @fblundun)

We're moving our endpoint away from /i

This change will affect POST requests. GET will remain the same.

Example:

http://d3rkrsqld9gmqf.cloudfront.net/com.snowplowanalytics.snowplow/tp2

https://github.com/snowplow/snowplow/blob/feature/0.9.7-new/2-collectors/clojure-collector/java-servlet/src/snowplow/clojure_collector/core.clj#L45

See:

• https://github.com/snowplow/snowplow-python-tracker/blob/a78da3a7ec58e3821158db96ce3c2e594b67e6f7/snowplow_tracker/emitters.py#L141

@fblundun can explain more on this.

As per snowplow/snowplow#722

With eid we no longer need tid. @yalisassoon can you confirm you don't use tid anywhere in the recipes/cubes/LookMLs?

There are incorrect uses of the schema key showing '$schema'. This should be changed to 'schema'.

Example: https://github.com/snowplow/snowplow-ios-tracker/blob/develop/Snowplow/SnowplowRequest.m#L121

NSMutableDictionary *payload = [[NSMutableDictionary alloc] init];
        [payload setValue:kPayloadDataSchema forKey:@"$schema"];
        [payload setValue:eventArray forKey:@"data"];

https://github.com/omergul123/LLModel

See #13 for resources

No idea if we are already doing this: http://stackoverflow.com/a/19190185/255627

Please close if we are already!

https://github.com/segmentio/analytics-ios/tree/master/Analytics/Helpers

Reason: gives clarity.

Similar to snowplow/snowplow-java-tracker#49

Setting to 0.2.0 for now, but shouldn't be difficult to pull forward.

It would be nice to create a way of doing client-side sessionization, somewhat similar to how the JavaScript Tracker does it:

The JavaScript Tracker sets a first-party cookie to track the Snowplow session. This
cookie is kept up to date with the latest activity. When there is a gap (of 30 minutes) in
activity, then the session index is incremented. This is sent through as vid here:

https://github.com/snowplow/snowplow/wiki/snowplow-tracker-protocol#15-user-related-parameters

It would be nice to do something equivalent for mobile. A few questions:

1. How should we define the end of a session? Inactivity? Backgrounding? Something else?
2. Should we make session definition customizable, or is that a world of pain?
3. Where should this live? Do we overload the vid field or add this to the mobile context? Overloading vid feels a little messy but semantically this is the exact same data: the session index for a given client platform

/cc @yalisassoon @azsmith

Would involve bundling the Estimote SDK (see ARanalytics for bundling sub-dependency) and wiring up some kind of trigger or hearbeat events.

Supporting materials:

• https://github.com/Estimote/iOS-SDK
• https://github.com/snowplow/snowplow-javascript-tracker/blob/1.0.1/src/js/tracker.js#L689
• https://github.com/snowplow/snowplow/blob/feature/0.9.4/0-common/schemas/jsonschema/com.snowplowanalytics/snowplow/screen_view.json

When we have a determined/unchanging schema for how the context 'co' is going to be set, we should consider refactoring our 0.1 implementation to be configurable or generic. Right now, it feels a bit hard coded and ugly to read.

Early thoughts:

• SnowplowPayload should be an object which always has schema with data configurable as an array or object.
  • This would let us have nested payloads (see example payload below)
• Fix inheritance from NSDictionary
• Add inits with default schema
• Solve how to make data optionally a dictionary or array ( EDIT: Use type id and check with [myObject isKindOfClass:[NSDictionary class]] )

{
    schema: 'iglu:com.snowplowanalytics.snowplow/payload_data/jsonschema/1-0-0',
    data: [{
        eid: 'BBBAEB98-B556-43E6-8A07-80B6FD093C2E',
        vp: '320x480',
        p: 'mob',
        co: {
            schema: 'iglu:com.snowplowanalytics.snowplow/contexts/jsonschema/1-0-0',
            data: [{
                schema: 'iglu:com.snowplowanalytics.snowplow/mobile_context/jsonschema/1-0-0',
                data: {
                    osType: '...',
                    osVersion: '...',
                    deviceVendor: '...',
                    deviceModel: '...',
                    carrier: '...'
                }
            }]
        },
        refr: 'myreferrer',
        url: 'http://foo.com',
        dtm: 1402062281979.792,
        tv: 'ios-0.1',
        tna: 'myname',
        lang: 'en',
        page: 'This is my foo',
        e: 'pv',
        aid: 'foo',
        res: '320x480'
    }]
}

Moving to a gitflow-like development approach (quite theoretical given small team size!)

http://nvie.com/posts/a-successful-git-branching-model/

In other words Content-type: application/json; charset=utf-8

Just for completeness.

Needed to avoid clashing between queries & removals.

See documentation Using FMDatabaseQueue and Thread Safety.

I'll do this today (Friday), but I'm adding it here as a reminder, shouldn't take too long.

While this isn't an immediate issue, some people's research seems to say that an async NSURLConnection has a 3-4sec performance hit. It might be worth doing similar research and considering the AFNetworking library.

Sources: Stackoverflow

See Fred's comment here

https://github.com/smyrgl/RESTEasy

Default to every 60 seconds. For reference:

Sample reference: https://segment.io/docs/libraries/ios/#how-can-my-users-opt-out-of-data-collection-

Reference issue #22 where we've decided to use the AFNetworking library to handle sending of events. If there's a need for using the native NSURLConnection sendSynchronousRequest:returningResponse:error: or NSURLConnection sendAsynchronousRequest:queue:completionHandler: to handle requests, comments should be added here.

Initial milestone is set for 0.3

We don't have a failure scenario if we're unable to send an event. This is probably related to #20 and #9 on how to handle this.

[manager GET:[self.urlEndpoint absoluteString] parameters:data success:^(AFHTTPRequestOperation *operation, id responseObject) {
        NSLog(@"JSON: %@", responseObject);
    } failure:^(AFHTTPRequestOperation *operation, NSError *error) {
        NSLog(@"Error: %@", error);
        //Handle GET error response
    }];

https://github.com/ylechelle/OpenIDFA

The default - (id) init doesn't set most required options which need you to use the setters (i.e. setAppId, setUserId, setNamespace, setCollector) but we don't check if those have been set before attempting to flush all the events.

We should log an error in SnowplowTracker to stop and throw an error if this happens.

As opposed to the preferred:

- (id) initUsingNamespace:(NSString *)namespace_
                    appId:(NSString *)appId
            base64Encoded:(Boolean)encoded
                collector:(SnowplowRequest *)collector;

Basic idea: at compile time, run some tests that the generated events conform to the JSON Schema they claim to.

Useful links:

• https://github.com/samskiter/KiteJSONValidator - for validating the schema
• https://github.com/mcandre/objcheck - for generating type-ranged data in Objective C
• https://github.com/Prismatic/schema/blob/d82bf0b049fc1205a81a79d88a84872bb9f9846b/src/clj/client/objc.clj - for some Clojure that auto-generates Objective C

I think lots of the other trackers use a SQLite to hold the outbound event queue.

We've used NSDictionary with SnowplowPayload in a few places. While it's only a minor issue now, it should be fixed to avoid confusion later.

This goes hand-in-hand with #34

See for an example: https://github.com/smyrgl/RESTEasy/blob/master/.travis.yml

NSString * const kSnowplowVendor        = @"com.snowplowanalytics.snowplow";
NSString * const kIglu                  = @"iglu:";

I'm not sure why I did this in the first place, but it should be removed or set in a better way by using setSchemaTag:.

See: L#36 and L#84

EDIT: I remember now.
We need to stick iglu to the end of the vendor. Change setSchemaTag to setVendorAndSchema(vendor, schema) (or something like that).

• vendor changes the whole url in case a user doesn't use iglu.
• schema is for schema of the payload.

One possibility: http://objcsharp.wordpress.com/2013/09/24/how-to-generate-beautiful-apple-style-documentation-in-xcode-5/

Final step pre-release

https://github.com/orta/ARAnalytics

/cc @yalisassoon