After reading this, it seems like one device can be used for multiple developer accounts.
I was worried when I started seeing “iCloud” because of course none of us use our personal iCloud accounts for dev work. However, it looks like you can link multiple dev accounts to your personal iCloud account to prevent having to sign in/out of the accounts on the device.
That does make it so you can get verification codes on one device for multiple accounts but it still requires you to log out of your primary (personal) account, log in with the dev account, enable 2FA and then log out and back in as your primary account. Then you still have to add the dev account to the "iCloud" login on your phone or similar so you can get verifications.
It all seems super hacky and like a total after thought versus a clean well designed system. I am happy Apple takes security seriously, but this doesn't seem very elegant or even effective.
And while I am not currently building apps for clients, it seems this will still be a hurdle for dev shops to overcome, since having the clients account 2FA to your device is not ideal in anyway. Would be curious how people are handling this. It could be I am still just missing something obvious.
We tried using Intercom as a “all in one” tool for support, leads, CRM, and it just wasn’t good enough.
We ended up getting Pipedrive for the CRM. Then we hooked up the new Pipedrive integration which is one click to generate a new user, and deal after they show interest with our bot or with us.
For support, we love it and so do our customers. I know there are a lot of chat solutions but it feels the best to me. The bonus is it is integrated with our Help Center (also Intercom) so it is very easy to send embedded articles right in the chat. Our customers love this :)
We are a small team and we were able to reduce the amount of support phone calls (they wanted a phone call to ask the simplist things) by answering quickly on live chat. This allowed us to be able to serve multiple customers at once in a async fashion.
We use Intercom for support and push SQL's into Pipedrive. It works great. It keeps Pipedrive clean and our Sales people focused on real opportunities. We use Intercom a lot for its "segments", and do a lot of personal mail from there. For example, we hosted a drink-up in Copenhagen one day and was able to quickly shoot an email to all customers living there in about 2 minutes. I used a filter to identify who hasn't used the app in a while, remembered their names, and inquired when I met them. I dig it for that.
I wonder if Uber/Lyft has seen a jump in driver sign ups since the shutdown. Not sure how fast their onboarding is...but probably faster than trying to find a new job / temp job?
Just a gut feeling. 7 kind of felt too short, and 14-30 a bit too long. We feel that you'll experience the benefit in 10 days. We can always adjust if needs be.
Too long by what metric? Personally, I dislike short trials. If I get distracted by something more important before I have time to fully investigate the product, I'm likely to just forget about it when the trial prematurely ends.
I don't think this solves the problem of people getting distracted. If I make 10 API calls and then get called away to do Super Important Thing for the next 6 days, I'm probably pretty likely to give up on a service if my trial period is reduced to 1 day.
Have you thought about N API calls for a trial? That's what I've used for API-first products in the past that worked pretty well for me.
No metric, again just gut feel. Overly long trials can also fall by the wayside. We don't particularly want a long sales cycle, but if near end of the trial, when you inevitable will hear from us, you'll know if you need more time or not.
Startups are an experiment after all, so let's see what works.
My thought for shorter trials: If something more important derailed the trial then the product isn’t solving a problem with enough urgency for you and you were unlikely to convert.
We launched a crime based RPG game on iOS back in the day that had a leaderboard which tracked in game net worth (cash, investments, etc).
I still remember the day we woke up to multiple emails and lawsuit threats from our top player whose net worth suddenly went negative on the leaderboard.
Our players were very competitive and loved pushing the boundaries by trying to find vulnerabilities, shortcuts, etc so we assumed the worst and thought we had a bug in our system! Turned out to be our JSON parsing library was using integerValue on our NSNumber instances causing the ints to overflow. It was a tough week waiting for Apple to review the app while our players lost faith in us.
Lesson learned :)
(Luckily the player and our community was understanding and stay around)
We launched a crime based RPG game on iOS back in the day that had a leaderboard which tracked in game net worth (cash, investments, etc).
I still remember the day we woke up to multiple emails and lawsuit threats from our top player whose net worth suddenly went negative on the leaderboard.
Our players were very competitive and loved pushing the boundaries by trying to find vulnerabilities, shortcuts, etc so we assumed the worst and thought we had a bug in our system! Turned out to be our JSON parsing library was using integerValue on our NSNumber instances causing the ints to overflow. It was a tough week waiting for Apple to review the app while our players lost faith in us.
Lesson learned :)
(Luckily the player and our community were understanding and stay around)
After reading this, it seems like one device can be used for multiple developer accounts.
I was worried when I started seeing “iCloud” because of course none of us use our personal iCloud accounts for dev work. However, it looks like you can link multiple dev accounts to your personal iCloud account to prevent having to sign in/out of the accounts on the device.