CommentComment

I got a few emails after my comments last week asking why I didn't mention Xcode for iPad. It's an interesting subject, but I deliberately didn't bring it up as I was primarily talking about the consumer perception of the iPad. But, I don't think the time is right for Xcode for iPad, and I'll tell you why.

What makes Xcode different from Swift Playgrounds? I think the biggest difference is that Xcode builds apps that run independently, whereas playgrounds are neatly self contained. Yes, of course there's more to it than that, but that's the fundamental difference.

So why don't Apple make Xcode that can build and install other iPad apps? Sure, they could. But what about iPhone apps? I'd say that until Xcode can build and deploy to other iOS devices, especially phones, it's probably not going to see the light of day. Can the iPad do that? Of course it can, but I don't feel like that's where Apple's priorities lie, or should lie, right now. For now, the Mac is an amazing platform to build iOS apps on and Apple are focusing on building the platforms out for consumers first. Us developers can come along later, it'll be fine. ๐Ÿ‘

Now, I could be completely wrong and I may be eating my words after next week's event, but I'd be really surprised if this is the year that happens.

Dave Verwer

News


Tools

Code




macOS Development


Jobs



And finally...