views:

84

answers:

2

A client do not want to consider MonoTouch for a new project.

MonoTouch.info has a long list of apps, but I have not found any on the caliber that can convince a client too choose a technology. The client has seen the list, and actually use the bland screenshots as an argument against MonoTouch.

Where can I find examples of applications useful as motivation. High profile apps created using MonoTouch, the apps you call home about. The apps that made it to the top 25 lists in their category.?

+3  A: 

Hi Peylo,

I responded on Twitter but thought I'd reply properly here;

The first app I will mention is iCircuit - http://icircuitapp.com/ - this application is featured on the Apple website here - http://www.apple.com/ipad/business/apps/index.html#workflow-icircuit - and is a pretty good seller.

Diggify is a Digg application which hit the top #8 sold application in Canada apparently - http://www.intomobile.com/apps/diggify/359756952/

An application that I built myself (it's a little old now admittedly) but I do think that it looks rather nice - http://bit.ly/gfxmasappstore :)

London Bike App is another nice looking application - http://www.londonbikeapp.com/

Hope this helps,

ChrisNTR

chrisntr
Sorry for not replying on Twitter. It is a good start, thanks.
PeyloW
I can't quite work out what exactly you're looking for. If one MonoTouch application can do X then potentially all MonoTouch applications can do X. Just because it hasn't been done doesn't mean the potential is not there. :)
chrisntr
@chrisntr: The client argues that MonoTouch while accessing the same API in itself is an obstacle for creating great apps. I want to argue that only the skill of the developer is a problem, not MonoTouch in itself. But it is hard argue when the majority of apps known to be made with MonoTouch in all honesty are crappy, or bland at best.
PeyloW
+4  A: 

I know of a couple apps that were built using Monotouch and sold very well but due to the uncertainly surrounding the terms when MT first came out and later the 3.3.1 mess the devs didn't make a big fuss out of it. I suspect they aren't the only ones not publicizing what technology they used to make their app.

If your client is using a handful of screenshots on a website as the reason to rule out using Monotouch then you might want to rethink your pitch. Whether or not an app has been developed in native Objective-C or C# via Monotouch makes no difference on the overall design or appearance because both rely on the CocoaTouch framework for UI. Being able to deliver an app that meets your client's idea of what makes a great app has nothing to do with the language you use and has everything to do with your ability to translate the essence of their ideas into a solid design and UX. Sell that, not the framework.

Kevin McMahon
I understand you point. But the client argument is along the same lines; "Both use the same API, so why are MonoTouch apps so bland?". I need examples to show that the blandness is not due to MonoTouch, but due to the crappy devs. Or I need a new pitch as you say, I am open for ideas.
PeyloW
Many of the MonoTouch developers that write those apps are here in stackoverflow, answering questions like this one. Saying that most of them are crappy is really not the most sane way of asking for help.
Eduardo Scoz