Thanks for the feedback - so far this hasn't been a barrier to our adoption, but we may provide source access as part of an enterprise package. Do you have some examples of SaaS companies that have succeeded with the model you suggest?
> If Canada wants to do something for startups, they should setup a sovereign wealth fund that does early stage investment in Canadian companies -- and then it should actively help make those companies successful.
The Business Development Bank of Canada (a financial institution owned by the federal government) actually does this - it has a venture fund that's one of the largest in Canada.
Wow, that's comprehensive. The Net Promoter survey is very powerful, if you've never used it: once you've identified and bucketed all of your users who give you a 9 or 10, you can hit them up for referrals, reviews, and shares, and skip all the users who might not have anything nice to say about you.
> You don't have to submit hour-by-hour breakdowns either. You submit what % of an engineers time was spent on SR&ED work and what the engineer's salary is. That's it.
OP here - the breakdowns and spreadsheets shown in this piece were designed by or with the CRA during the CRA's technical audits of one of my companies. The evidence log screenshot, for instance, was a template provided to us during the technical review that we were required to complete. (The claim was eventually accepted unadjusted FWIW.)
I use it (with Recurly). It's fantastic, especially since Recurly's built-in reports don't seem to jive with reality (for instance by ignoring coupons on subscriptions). The multi-user support and email alerts are also useful.
These links don't preserve intent for users who don't already have the app, due to the App Store's and Google Play's problems with attributing app downloads.
My company, Tapstream, fixes this by pairing our attribution platform with a deep link redirector - users who have the app already are deep linked, and users who don't have the app are sent to the App Store.
Giving marketing teams the ability to test and optimize transactional emails opens up a new customer referral and upgrade channel. Love what these guys are doing.
> I can't think of a really good legit reason for wanting a cross-app unique ID.
The use case that's affected the most by this change is that of advertisers who want to track the performance of ads they buy from publishers, which I think is a legitimate need. The fact that the IDFA uniquely identifies an iOS device (unless the user resets it) is a side effect of Apple's implementation of it; all app advertisers really want is the same kind of first-party conversion tracking for their apps that's standard everywhere else on the web.
Allowing the use of the IDFA by publishers and not by advertisers renders it useless, since it can no longer be used for attribution. I don't think conversion tracking - measuring the performance of ads you bought to promote your app - counts as spying.