Commenting here for posterity. My money is, unfortunately, on Apple screwing you guys over within the next year. Likely right before they launch a tool of their own that only does a fifth of what Workflow does.
UPDATE: I was able to get siri support by creating a contact called "Workflows" and adding the x-callback-url as a URL for the contact. I can say "Workflows" to Siri and she will show me a list of all my workflows, and I can select the one I want from a list.
The only tricky part was getting the x-callback-url out of the data: URL since the contacts app won't open data: urls. Yay!
PS. I LOVE this app so much. Thank you thank you thank you thank you!
This is incredibly clever. We have a completely separate, but equally crazy hack that we were thinking of using to implement this. But well done. And so glad you like it :)
UPDATE 2: I was nearly able to create a workflow to create a contact automatically. Unfortunately the "get contents of url" task doesn't support data URIs.
Can you not create a home screen link directly to the app?
<10 minutes of playing around with the workflowFEC418 url scheme>
Well darn, it looks like you can't. That's crummy. I thought I could get clever with `history.pushState`, but that doesn't let you change the URL scheme without a security error. It looks like this is the best way to do it on iOS.
You're misunderstanding what the OP is saying. He/she is pointing out a logical fallacy in the App Review rules.
Developers are allowed access to something called an "advertising identifier" which lets them track users between apps, for the purposes of targeted advertising. Apple is very restrictive in terms of user identification, in order to protect users' privacy, so this is the only way to uniquely identify a user/device, and the user can optionally opt-out of the advertising identifier entirely.
Apple doesn't want developers to use the advertising identifier for things other than advertising. But the way they enforce this is simply by requiring that an app include ads in order to use the advertising identifier. If you use the advertising identifier and your app doesn't visibly include ads, it will be rejected.
This restriction is ostensibly intended to prevent developers from abusing the advertising identifier, but really it just encourages developers to include shitty ads in their apps, because if you include ads, you can use the advertising identifier for whatever you want behind the scenes. It's a nonsensical way of enforcing this policy. Thus, "security theater."
Awesome, thanks for the advice. We were looking into alternatives for algorithms that better reflected human color interpretation, and that looks very helpful.
And yeah, your games are awesome, we basically modeled this as "the Kerning Game/Color Game, but for brands."
A three-slider HSL color-picker. It was really hard for my co-workers and I to pick the right hue without worrying about dealing with the saturation too. I'm used to color-pickers so it wasn't as bad for me, but they kept thinking they could use more inner/desaturated colors and then just tweak the darkness to accomodate for the lightness they didn't realize was happening.
This article is very vague and confusing. I'm sure there are real problems here, but the grammar makes this hard to read. What are you complaining about, specifically, in the "Logos" section? What would you like a company like Twitter to be providing in terms of graphics?
