[bradleyjoyce]

I absolutely love the idea and the look/feel of this app. When I first heard about it I thought... this is what I've been looking for.. an easy way to auto capture and generate all these important metrics!

So I got started immediately with integrating it into TweetSaver. Unfortunately, I ran into a show stopper pretty quick.

When passing a signup event, they require you to send a unique username. This was a major bummer since for the free level of my app, users are not required to give an email address and in general emails may not be unique to a user in the system. This essentially renders sunnytrail unusable for me.

The best part though is that co-founder Octav is always in the live chat on the site, so I explained my situation and he said they would take a look to see if there is a better solution. I'm anxious to see if they can make some changes that will allow me to use their service!

[andreisavu]

Hi Brad! I'm glad you like Sunnytrail. Your problem can be easily solved. I suppose that you are generating for each users some sort of unique ID. My advice is to use that to generate an username (if not already available) and a dummy email address. You should be able to update those later when that customer upgrades to a paid plan. TweetSaver looks great! Get back to us on email if you've got more questions.

[bradleyjoyce]

that feels pretty hacky to be honest.

the real issue is that one person may have multiple accounts in the app, and they may want to use the same email address for all accounts... I have no reason to enforce a unique email address.

It's odd that Sunnytrail would when there is usually a common unique identifier across all apps for users.. user id

[andreisavu]

Sunnytrail does not enforce an unique email address or an unique username. We are tracking users based on the supplied internal user ID (or an email address hash if an internal user ID is not provided).

[bradleyjoyce]

hmm, I'm pretty sure that's what Octav had told me in chat.. either way you require an email address...

    RuntimeError: The request is invalid: {"message": "invalid JSON message", "errors": [["", "A valid email address is mandatory"]]}

[andreisavu]

required but not unique. just generate a dummy one based on the user id.

[bradleyjoyce]

so just really curious.. what's the reasoning behind requiring it?