6 ms·
Apple: .net apps are kicked off iPhone OS 4 too.
- jaustin 17y agoI can't work out how 'official' that statement is, especially given that it conflicts with what Unity have apparently said (perhaps there are updates on that story that I've missed?) - http://techcrunch.com/2010/04/08/adobe-flash-apple-sdk/ http://techcrunch.com/2010/04/08/adobe-flash-apple-sdk/ There seems to be an 'official' response from Novell here: http://www.mono-project.com/newstouch/archive/2010/Apr-09.html http://www.mono-project.com/newstouch/archive/2010/Apr-09.ht..., but the email linked here is doing the rounds on blogs/aggregators as an 'official statement' - is that guy one of Novell's lawyers? Further to the link this post gives, this email form later in the thread is useful/gives more context: http://lists.ximian.com/pipermail/monotouch/2010-April/001882.html http://lists.ximian.com/pipermail/monotouch/2010-April/00188...
- nailer 17y agoIt's from Steve Jobs email account (perhaps I should change 'Apple' to 'Steve Jobs' to make this apparent, but it's too late) The relevant part: .net dev > So, I replied back to him, and explained that my firm intends to both create in-house applications, as well as distribute apps via the app store: Steve Jobs > (Paraphrasing his reply:) "Sorry, if you use the app store, you need to adhere to the T.O.S."
- TomOfTTB 17y agoThe problem I have is that you paraphrase. For something so important I think it would be worth publishing the whole e-mail. Unless there's something personal in it that you don't want to share.
- nailer 17y agoI'm not paraphrasing, I'm directly quoting the .net developer who mailed jobs. He is paraphrasing.
- stuaxo 17y agoHe just refers back to the TOS, we really need someone to ask - "Can we develop with Monotouch?" and a statement of - "This breaks the TOS" Not just saying "if it breaks the TOS"
- voidpointer 17y agoAs far as the statement from unity is concerned, it sounded like it wasn't really backed by any real indication from Apple about their solution not being banned. However, there is also no actual evidence (yet) that it is actually banned and that Apple will enforce the ban. Consequently, as they are about to ship a new release, they want to sound as confident as possible. I am very doubtful though whether they have any real idea regarding if and how they will be affected. I think they're mostly trying to prevent panic.
- alnayyir 17y agoIs there anyone who actually makes a living off of iPhone development that was affected by any of this? Can anyone honestly speak to this being a problem?
- nailer 17y agoExcerpt: 500 apps in the App Store are built on Mono and Unity3D alone. That's excluding non-3D apps. Source: http://www.mono-project.com/Software http://www.mono-project.com/Software Presumably these would all be affected.
- gte910h 17y agoIronically, with the huge bevy of crap out on the store, I think the majority of cross platform library apps are likely currently higher average quality than the actual "Average App". Unity3D especially raises the bar there. --Actual Developer
- StrawberryFrog 17y agoI can't speak personally, but somewhere in this video http://live.visitmix.com/MIX10/Sessions/EX02 http://live.visitmix.com/MIX10/Sessions/EX02 Miguel mentions the number of top 100 iPhone apps that use MonoTouch. I think it was about 10. So based on that - yes, it will affect some iPhone developers, and the argument that this move by Apple is about quality is bogus.
- wvenable 17y agoIf 10 .NET apps in the top 100, this is going to affect a lot of users as well.
- veemjeem 17y agoIf you have a top 10 app on the app store, it's likely that you'll probably do the legwork to port the app to whatever language is necessary to run on the platform. It's probably a poor business decision to just "give up" $5000 per day of revenue because you need to rewrite the app. There are many developers that would love to take trade places with those 10 apps in the top 100. If I knew something like Doodle Jump was written on the .NET platform, I'd probably jump at the chance to make a similar clone in hopes of taking it's place.
- voidpointer 17y agoIsn't it funny how many people using alternative runtimes seem to say "I can fully understand why they would ban Adobe/Flash but why on earth would they also ban my favorite runtime"? Apple didn't make this move because they have some irrational religious hatred against Adobe. They are just betting that a tight control over the technology by which people produce applications for their mobile platform will be advantageous to them. They are fully aware that this is bad for people who have bet on using different technology and I guess is that they just don't care the tiniest bit.
- chops 17y agothis is bad for people who have bet on using different technology Absolutely true. An intersting thing is that I, and I'm sure quite a few others, would never have guessed that language choice was a "bet" (at least, not this kind of bet, anyway).
- voidpointer 17y agoNeither would I. When analyzing risk, there is also always the risk that you didn't recognize something as a risk at all. Maybe this is the Black Swan event (http://en.wikipedia.org/wiki/Black_swan_theory http://en.wikipedia.org/wiki/Black_swan_theory) of mobile application development... Unlikely but disastrous at the same time...
- rbanffy 17y ago> I (...) would never have guessed that language choice was a "bet" Oh boy... It took years for me to convince several companies Java is not the only language that can turn out "enterprise level" applications... That risks putting me back in square one. Thanks, Steve. Well played.
- chops 17y agoOh boy... It took years for me to convince several companies Java is not the only language that can turn out "enterprise level" applications... No doubt, but that's a different kind of "bet" (I briefly alluded to it in my original comment). There's naturally the bet that the language might not be around in 2 years, or that the language isn't capable enough to do what you need it to do, or that the language is too niche for XYZ Corporation's programmers and finding other programmers might be hard[1]. But that's a completely different kind of bet from "I wonder if this very popular and capable language will be against the arbitrary and ever-changing rules." The former is quite practical. The latter shouldn't have to be a concern. [1] Off-topic, I recently had this debate with a guy I'm going into business with, in which I was trying to convince him Erlang is a viable language. He's more of a business-financial-type and was concerned with the proverbial "what happens if you get hit by a bus." While I understand his concern, eventually he, correctly, resigned the programming stuff to me, where it belongs :)
- clawrencewenham 17y agoI work in IT, where we use C# and .Net exclusively, and would love to develop iPhone apps in MonoTouch. However, I also think Apple is doing the right thing by banning "meta-platforms" from the App store. Adding layers of abstraction that only serve the developer, rather than the phone's owner, is hard to justify on small, battery-powered devices. Especially when introducing multi-tasking features, RAM becomes even more precious, and fameworks, interpreters, cross-compilers, etc. will cause a bloating trend. If OS 4.0 does indeed make it easier to deploy IT apps across the enterprise without going through the App store, and 3.3.1 only applies to the App store, then I know my problems are solved.
- davidw 17y agoI think some form of "caveat emptor" would be more appropriate than simply banning stuff. One man's bloat is another man's lower barrier to entry for an app that he really wants to write, but has trouble writing in ObjC. Maybe it's supremely useful for a niche group of users because the author is an expert in some domain...
- clawrencewenham 17y agoI hate to say it, but that actually sounds like another excellent reason to keep that developer out of the market. Remember that the App Store is a business and a marketplace, where products are being sold to real consumers who want their phone--and everything that runs on it--to be reliable. IE: this is a professional realm. Professional programmers don't have a problem with learning a new language, if that's what's required to target a new platform. If someone "has trouble writing in ObjC", then they really need to work on their skills. This person sounds like a hobbyist who probably shouldn't be selling his wares to run on consumer electronics devices with limited RAM and battery life.
- davidw 17y agoI'm not talking about professional programmers. Here's a use case: someone in a niche field - say, an archaeologist, just to pick something - has a clever idea for a phone app that will assist him in his job. He knows a little about programming, and manages to put together a Lua script that does most of what he needs. Several of his colleagues find his code really useful and recommend it to their friends too. You're probably right that the app store isn't the right place to distribute it, but Apple doesn't give you a lot of leeway there, does it? In any case, if it's some random app for a niche, and people find it useful, who cares if it's got some deficiencies?
- sh4na 17y agoA post on a mailing list from someone who emailed "Steve" and got some one-liner reply does not strike me as an official announcement from Apple, no matter how much people enjoy saying "ooh, I mailed Steve and he replied, I'm sure this matter is over and done with now" There are way too many companies and users affected, for this to be resolved via some one liner reply to some guy on a weekend. A bit obvious, eh?
- pyre 17y agoI'm sure whatever was emailed back is the current 'official line' of the company. They may change that if there's enough developer push-back, but unless you're trying to claim that Steve (or an underling) responded with something that isn't 'towing the company line,' then this should be pretty inline with the message that Apple wants to send. Just because it didn't go through some official PR channel means nothing.
- stuaxo 17y agoWe really need them to specify for each tool that we ask Yes/No - not to just refer us to the TOS.
- elblanco 17y agoAnybody know if this rule change is retroactive? Will Apple now go through the App Store and cleave out all the apps that don't fit this requirement? I'm betting there are a fairly large number of popular and high quality apps that don't fit into this prescribed tool-chain.
- yason 17y agoI never got excited by the iPhone OS, then I was a bit unsure for a while, but now I know again why I wanted to miss that boat. Well, more land for Android.
- veemjeem 17y agoIn other words, you were never a developer/user for the iPhone, and now you still won't be.
- yason 17y agoPretty much, yes. It never excited me and I never figured out why would it be cool to write iPhone apps. And that was at the time when iPhone was cool and Apple was still seen as benign. I was never a developer/user/anything to Java either and I've only later learned that I certainly didn't miss anything. ;)
- zandorg 17y agoI had a friend criticising me for writing my 'app' (an email archive and indexer) in C++ not C# because it "didn't use .NET". I replied that as it runs on a Windows 98 box with 128MB of RAM and a 400MHZ CPU, it's perfect to put on the iPhone. Of course, my GUI is not Apple-type polished and would never get accepted, but at least everything else is fine.
- endgame 17y agoWhat I don't understand about this whole kerfuffle is that Apple already had the power to arbitrarily block applications. Why not just make the TOS more explicit in requiring performant apps that look and feel like apps written in ObjC? That would still make life very hard for cross-platform flash, but allow people developing against Apple's library directly in Haskell, Scheme or whatever to do so.