tag:blogger.com,1999:blog-6621561.post2850597369742258773..comments2023-11-03T05:56:36.182-07:00Comments on ConceptDev (Craig Dunn's blog): MonoTouch/MonoDroid and Xamarin - what now?Craig Dunnhttp://www.blogger.com/profile/09377896535933926653noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-6621561.post-13900892469867603822013-03-27T09:17:43.848-07:002013-03-27T09:17:43.848-07:00Sorry I didn't see this comment earlier. You *...Sorry I didn't see this comment earlier. You *can* rely on MonoTouch (now Xamarin.iOS) to be ready and stable. As it turns out, for the iOS 5, iOS 6 and iOS 6.1 releases, Xamarin had a release ready within 24 hours of Apple publishing their final version.Craig Dunnhttps://www.blogger.com/profile/09377896535933926653noreply@blogger.comtag:blogger.com,1999:blog-6621561.post-22207444182499447152011-06-14T05:29:20.688-07:002011-06-14T05:29:20.688-07:00I second Mitch. apple does'nt accept anymore a...I second Mitch. apple does'nt accept anymore apps nont tested with the last version of Ios. wht will we do in september, when ios 5 will arrive and Monotouch will not support it?<br />We can't bet on Xamarin being ready and stable for september.<br />And, if it is unlikely that Attachmate will sue Xamarin, it is possible, and that would create big problems for developers who have to publish an app.<br />I have to publish an application by the end of september, so for now I will go on the objective-c side.nonsohttps://www.blogger.com/profile/02285632198630514119noreply@blogger.comtag:blogger.com,1999:blog-6621561.post-22013856093597362212011-05-23T04:21:16.966-07:002011-05-23T04:21:16.966-07:00Mitch, I think it's pretty unlikely that a new...Mitch, I think it's pretty unlikely that a new iOS release will break existing apps or prevent you working with existing MonoTouch apps. MonoTouch is built on the same APIs that Objective-C developers are using - and Apple doesn't (generally) want to break things for everyone!<br />Of course, any *new* iOS features are unlikely to be supported by MonoTouch... for that we'll have to wait and see what Xamarin comes up with.<br /><br />Jan, I don't know what the situation with Unity3D is... perhaps they have some info on their website?Craig Dunnhttps://www.blogger.com/profile/09377896535933926653noreply@blogger.comtag:blogger.com,1999:blog-6621561.post-40033860132506624712011-05-21T05:31:26.999-07:002011-05-21T05:31:26.999-07:00What about unity 3d ? - since mono is open source ...What about unity 3d ? - since mono is open source that should be unaffected :SJan Bæchhttps://www.blogger.com/profile/15061301618477571299noreply@blogger.comtag:blogger.com,1999:blog-6621561.post-52638696121042569922011-05-19T10:53:56.274-07:002011-05-19T10:53:56.274-07:00My concern is support for IOS releases during the ...My concern is support for IOS releases during the next 6 months before Xamarin (optimistically) has an alternative solution.<br /><br />How likely is it that some IOS release breaks some or all of MonoTouch-deployed apps?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6621561.post-86069264615163152522011-05-18T15:57:06.597-07:002011-05-18T15:57:06.597-07:00Point taken Craig, I hope you're right! I thi...Point taken Craig, I hope you're right! I think monotouch is mature enough that, for a good year at least, it can be a solid platform as is, and I think the mono folks will still be hanging around IRC to answer the odd question. <br /><br />What made me speculate as I did was Attachmate's odd behavior - why hang on to the IP at all if they have no plans for it? Somebody commented on Miguel's blog about Xamarin possibly acquiring the IP from attachmate, and Miguel replied that they weren't being cooperative, if memory serves me right. So, one possible reason to hang onto it is to litigate later. Another possible reason is that the action is truly incoherent because attachmate is a big bureaucratic dolt, which is also totally plausible.Mikehttps://www.blogger.com/profile/10109352424128993249noreply@blogger.comtag:blogger.com,1999:blog-6621561.post-1523137603622177872011-05-18T07:47:44.712-07:002011-05-18T07:47:44.712-07:00I trust Miguel and team to be true to their word. ...I trust Miguel and team to be true to their word. I would suggest people continue work on MonoDroid and then migrate to the Xamarin stack. It definitely beats writing Object C and Java.<br /><br />Just my 2 cents.MitchLhttps://www.blogger.com/profile/08542308357563212254noreply@blogger.comtag:blogger.com,1999:blog-6621561.post-21321067723486947272011-05-17T16:46:52.530-07:002011-05-17T16:46:52.530-07:00It's true there are still a lot of uncertainti...It's true there are still a lot of uncertainties, however it seems pretty unlikely that Attachmate would be so 'cunning'. It would have been a lot easier for them to keep the team and product in-house than to (a) sack everyone and let the product die then (b) secretly hope that they'll create a startup, manage to successfully clone the products, create a large market for said clones and THEN (c) after all this is done come back and sue.<br /><br />Right now I think the main issue for existing customers is support - it probably doesn't exist (except through the community and the good grace of the team) and there probably won't be any upgrades/updates. You have no legal issues continuing to use MonoTouch & Mono-for-Android as-is. You purchased them from Novell and are licensed to use them for as long as you like - nothing has changed there.<br /><br />Worry about the rest when there is something concrete to worry about.Craig Dunnhttps://www.blogger.com/profile/09377896535933926653noreply@blogger.comtag:blogger.com,1999:blog-6621561.post-56049390025255906602011-05-17T06:42:03.279-07:002011-05-17T06:42:03.279-07:00I have confidence in the Mono team and in the code...I have confidence in the Mono team and in the code compatibility between what they produce and the current touch/droid products. So, because I own both of these, I think going ahead with current plans is a sound decision, except... I have a sinking feeling that attachmate might be planning to wait for xamarin to see some success, and then sue the crap out of them AND their customers. As long as we don't know what the legal situation is, all mono on mobile developers have a sword of damacles hanging over us.Mikehttps://www.blogger.com/profile/10109352424128993249noreply@blogger.com