Here's how I look at it. If I was going to write an app, I'd probably go the whole route and make the purchase of a Mac, used or new. However, I am currently in the process of learning C#, so the ability to port C# to IOS is particularly attractive to me, especially as I would not have the history or marketing power of some of our more respected and established developers. I would have to build up that rep with PC games, and then I could either focus on Objective C for a while, or I could spring for the C# port. There is one thing to keep in mind. Learning Objective C is maybe pretty difficult. It's not like many other languages, but Apple itself offers a lot of free resources to people who're interested in Objective C, and downloading courses from the ITunes University, which are also free, can really boost your knowledge. If I wasn't actively learning C#, I'd be learning Objective C, because right now, and for the foreseeable future, and without opening too big of a can of worms, IOS is the most accessible handheld device, in terms of what it can do and how it is used.
Also, Java is riddled with security holes, and unless someone has had professional training in development, they probably are going to miss at least a couple. This can be a really big issue for a person owning a phone, wherein they keep a lot of valuable data, just as it can be an issue for anyone on a computer. Thus, while you can write apps in Java for Android devices, Oracle is only just now really stepping up to the plate in terms of security, so that is a consideration, whereas all Apple apps are basically sand boxed. It'd be really hard for someone to screw up enough in programming that a security hole was left open enough to allow user data to be compromised in anything other than that one app. Signed: Dakotah Rickard On 6/7/13, Thomas Ward <[email protected]> wrote: > Hi, > > Agreed. While there are sometimes compatibility issues I haven't > noticed it being quite as bad as Trouble's message might indicate. > Plus if a developer specifically makes sure to list the system > requirements for known compatible phones, Android OS minimum version, > then I don't see this massive compatibility problem he is talking > about. If the developer's site says Jellybean or hire and someone > tries to install it on Ice Cream Sandwich then the user might have a > problem, but that's not the developer's fault as they gave the system > specs on the web page and they were ignored by the user. What more can > you ask for? > > Cheers! > > > > On 6/7/13, Willem Venter <[email protected]> wrote: >> Trouble, at worst you might have to have a second user interface for >> older versions of android, but usually if you write software for >> android it can just run, because it is just a normal java program >> using the android API. The problem of "fragmentation" on android is >> not as bad as it is made out to be by some. >> > > --- > Gamers mailing list __ [email protected] > If you want to leave the list, send E-mail to > [email protected]. > You can make changes or update your subscription via the web, at > http://audyssey.org/mailman/listinfo/gamers_audyssey.org. > All messages are archived and can be searched and read at > http://www.mail-archive.com/[email protected]. > If you have any questions or concerns regarding the management of the list, > please send E-mail to [email protected]. > --- Gamers mailing list __ [email protected] If you want to leave the list, send E-mail to [email protected]. You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/[email protected]. If you have any questions or concerns regarding the management of the list, please send E-mail to [email protected].
