Thoughts on MonoTouch

As you likely have heard, Attachmate let go of the entire Mono team recently, including all the outstanding people that created and supported MonoTouch. This came as a shock to many, including me, for a variety if reasons:

• There are many existing customers of MonoTouch.
• The community around MonoTouch loves the product.
• There have been some nice success stories recently of apps built with MonoTouch.
• The team that developed MonoTouch and Mono for Android are top-shelf developers.
• Several new books were near release for MonoTouch and Mono for Android.

I got involved with MonoTouch at the beginning of the first beta. I had already been doing some iPhone work with Apple’s tool chain and was (and still am) quite happy with it, but since I have always liked the C# language and .NET, I thought this would be an interesting technology to try out. Initially I was mainly intrigued with the fact that they could even create such a product from outside of Apple. As I learned more about it, I was nothing but impressed with how nicely they blended the C# language with CocoaTouch. All the knowledge I had from the Objective-C side was totally applicable, but I suddenly could bring other technologies to the table, such as being able to take advantage of nice C# language features like Linq, the ability to reuse non-UI code and additional library support via Mono’s implementation of the .NET framework class libraries.

As the technology builds on Apple’s stack, I didn’t have to trade away platform capabilities in any way. At the same time, I found a vibrant community of like-minded developers both from the Mono team as well as outside. I was having such a good time with the technology and the community that I decided to take some time to write about it a little bit on this blog, which eventually led to a book project with Addison-Wesley. I couldn’t have been more excited.

Then, in April of last year, Apple introduced licensing changes that effectively prohibited the use of technologies such as MonoTouch. Although in practice nothing ever got rejected for being built with MonoTouch, the looming threat of this resulted in my book project being placed on hold. I kept doing MonoTouch on my own, because I truly enjoy using it and participating in the community. However, business interests that I was doing MonoTouch development for, quite reasonably, could not proceed with such ambiguity, resulting in my moving some work over to Objective-C.

As you may imagine, I was pretty disappointed by all this, but then late in the summer, Apple changed the licensing again and everything was set back in motion. Excited as ever, I turned my attention back to reworking the parts of the book I had already written for the changes that came out over the time I was in limbo, and proceeded working on the remainder of the book. This work took me up to the end of last year, with the technical review following earlier this year. The book has entered the production process with my publisher and I’m proud of the result and grateful for all the fine people that helped me along the way. My publisher was planning a summer release, which would put the book out around the time of the upcoming Monospace conference. Things were looking great.

Then all these great Mono developers got laid off. First and foremost, I feel awful for any of the great people on the Mono team. They do spectacular work and provide amazing passion with everything they do. Such a team should have a better fate. As it turns out they just may.

Never one to give up so easily, not in the face of licensing issues and not even now with the entire team being dismissed, Miguel and his team are spinning up a new company, Xamarin, to continue what they started. He announced, among other things, that they would be bringing a new iOS product to the market that will be compatible with MonoTouch. This leads me to the current plan for my book.

UPDATE: My publisher has decided to send the book to print. It will be in available in bookstores by late July.

After discussing all the options with my publisher we have decided to go forward with the book in electronic form for now. We will be holding back from doing a print copy until more details emerge regarding Xamarin’s new offering. If we were to go ahead and print the book now it would be, well, printed. By sticking with an eBook we can make the information available to the many existing people using MonoTouch and still potentially offer an updated version for the new product in the future. I’m personally looking forward with great excitement to see what Miguel and his team create next.

6 thoughts on “Thoughts on MonoTouch

  1. Thanks for the news. Given the momentum behind Mono, Monotouch and Monodroid, why did Attachmate decide to layoff the entire team?

  2. I will definitely be buying the book, I am having great fun developing with Monotouch.

    Hopefully things will kick on with Xamarin, and when Monotouch is replaced/upgraded, you will get the book in print like you deserve.

  3. Mike –
    Thank you for your ongoing support of MonoTouch. This whole episode has been very shocking and distressing – in a million years, I won’t understand why Novell/Attachmate are dumping this valuable product/technology. I think that one of the things that has hurt MonoTouch is that you have to have a Mac to develop for it – and that hurt its marketability somewhat. I understand, from a technical standpoint, why this was necessary, but I do think that it introduced a steep bar for a .NET developer who wanted to try their hand at iOS App creation.
    Hey – I would like to support you and buy your eBook. I have bought several PDF eBooks from Addison-Wesley and been very happy with them. I buy them from http://www.informit.com But when I go to buy yours, the process is different somehow, and instead of just being able to buy the PDF, it seems like I have to go through Safari Online. A couple of years ago, I signed up for a trial Safari Online account, and never did anything with it. But the fact that Safari Online “recognizes” me as an expired trial user, is preventing me from buying the eBook. Any reason why I have to go through Safari Online, vs. just buying it as a regular PDF eBook?
    Thanks a ton,
    Jeremy Ellis

    • Hi Jeremy,

      The version currently on Safari Books Online is the “rough cuts” version. My publisher will be releasing the final version in July, which will include ePub, Kindle, Nook, PDF, and Safari Books Online.

      Thanks,
      Mike

  4. Hi Mike –
    I am still watching for the final (non-“rough cut”) version of your book to be available – it looks like it will be available near the end of this month.
    I just have one concern:
    I understand that this could be incorrect preliminary info, but it looks like your publisher will be making this available as an Adobe DRM eBook, instead of as a straight PDF eBook. Here is where I am looking:
    http://www.informit.com/store/product.aspx?isbn=0131388258

    My experience with any type of DRM on eBooks is bad. I like to load PDFs on my Kindle DX for reference, and I have compared MOBI and PDF formats, but I feel that PDF is closer to how the print book looks. I don’t like how the Kindle re-formats non-PDF books (as compared to the print version). However, lately, I have been reading most of my eBooks using GoodReader (a PDF reader) on the iPad. Though I keep my Kindle up-to-date as a backup, I really like the iPad/GoodReader solution. But any Adobe eBook with any type of DRM enabled invariably has problems on one or both of these devices. So, I have started to stick with just straight PDF. Usually, the publisher watermarks eBooks I buy with my name/address/e-mail address, so they can trace it back to me if I share it on the Internet – and that is fine, I think that is a perfect way to protect their property.

    But I really don’t like dealing with any type of DRM scheme on eBooks. So, I hope your publisher will keep that in mind when deciding what formats to make your book available in.
    Thanks,
    Jeremy

  5. Hi Mike –
    I still want your book, but I just can’t understand why it is not offered as a watermarked PDF instead of an Adobe DRM version.
    InformIT (and related imprints) have many, many great ebooks available for purchase as watermarked PDF files. I know, because I have bought many of them. Why not your book?
    Jeremy

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s