What iOS Can Learn from Unix
blog.inkmobility.com
What iOS Can Learn from Unix
1–10 of 59 posts
Re: What iOS Can Learn from Unix
#2Re: What iOS Can Learn from Unix
#3Android has this in the form of intents. Not quite as useful, but still works well. Maybe look at more than just iOS when talking about "the mobile space".
Re: What iOS Can Learn from Unix
#4Re: What iOS Can Learn from Unix
#5According to Michael, it's creator, it uses Mach Ports to communicate between apps. Apple embraced it and included it with GarageBand.
Re: What iOS Can Learn from Unix
#6I've posted this before, but it's relevant to mention AudioBus which is a way to pipe separate music apps together on one iOS device. I've incorporated it into one of my apps and it works really well. According to Michael, it's creator, it uses Mach Ports to communicate between apps. Apple embraced it and included it with GarageBand.
Re: What iOS Can Learn from Unix
#7Having concept of "files" to be able to open pdf you just downloaded from email/browser inside pdf reader?
Re: What iOS Can Learn from Unix
#8Re: What iOS Can Learn from Unix
#9It is a shame that we can't get more app functionality sharing in place, but really I don't know if we necessarily want to bring that much dependency management into the mobile space at large either.
Re: What iOS Can Learn from Unix
#10So really this is, "What iOS can learn from a 2008 Android device"? The author is wrong in his footnote. Android intents are both action and file type based or even wildcard URL based. http://assets.sbnation.com/assets/1219228/complete-action-an...