4 ms·
An interesting thing about this is that it could actually benefit ARKit by making it less risky. If you develop an ARKit app now, you can be pretty sure you'll
by iainmerrick 9y ago
An interesting thing about this is that it could actually benefit ARKit by making it less risky. If you develop an ARKit app now, you can be pretty sure you'll be able to port it to Android in a year or two as ARCore rolls out.
- briandear 9y agoWhy would it be risky anyway? Are app developers really counting on device parity between iOS and Android? Are developers not going to release something great because there is a potential Android wouldn’t support it? If feels to me that there is more risk in developing to the lowest common denominator — not creating something useful because of the potentrial it won’t work on Android.
- davidmurdoch 9y agoIt's risky in that you'd be developing a product that can't be "sold" to both markets. If you have two seemingly viable ideas for an app, and one can reach both platforms, while the other only one, you'll likely choose the former.
- iainmerrick 9y agoARKit could be a flash in the pan, I'm thinking. But a) Google is taking it seriously, and b) Android will have something very similar soon. Edit to add: I think a good comparison would be building an app around iOS force touch, or Macs with the touch bar. Those seem riskier.