Thanks folks, I've forwarded the replies to my colleague who manages these
matters. Lots of new jargon and ideas for us to digest -- Greg
On Tue, Jul 10, 2012 at 5:55 PM, Emily Waghorne wrote:
> Native iOS is considered the way to go if you want to be taken
> seriously by iPhone and iPad users but it depends a bit on your app
> and your target audience. And a web based solution is definitely much
> easier! (Consider android, windows
My understanding of Mono is that it only supports a subset of the iOS
functionality, so check to make sure what you want to use is made
available.
Native iOS is considered the way to go if you want to be taken
seriously by iPhone and iPad users but it depends a bit on your app
and your target audi
I'm the lead developer on the mobile products at my company.
For c# there's the http://xamarin.com/ company that sparked from the mono
project, it claims it works for cross platform development.
Apart from that you basically have two options: 1) Native ios/andriod 2)
wrap up a html5/javascript ap
> ** **
>
> The second question is a doozy and out of my areas of experience. Can
> someone confirm that .NET and the runtime is not available for iPad or
> iPhone? What kits and languages do you use to write iPad and iPhone apps?
> Is Object C still for that sort of thing? Or Java? Or HTML5? If an
Folks, we have a working Silverlight 4 app out there at the moment with some
desktop support apps all written in .NET 4. Now and then when we demo the
SL4 app someone will ask variations on these questions:
"...what's your migration path away from Silverlight when it dies?"
"...will the app
