My advice: learn iOS development
-
The power of Discord is limitless.
-
Because there's only so many ways to make square icons consisting of circles, squares and colorful highlights?
I'm not a designer...
-
It's nice, but without a large hardware company to adopt it, any OS is doomed to fail.
-
@tarunik said:
I just wish that learning how to write C# atop Mono didn't throw you at odds with every C# book out there...
Really? I'd be interested in hearing more about this, since that doesn't make much sense. The best C# books are the language spec and Framework Design Guidelines anyway.
Indeed. Care to elaborate, @tarunik?
-
Well, Discord is Q.
-
Indeed. Care to elaborate, @tarunik?
Well, the C# books I've run into start off with a quite Windows/VS-centric explanation of things, even when they're written for programmers, not noobs.
Besides -- I only really want to learn C# in order to learn the .NET framework libs, which seem to be designed in a C#-centric way -- are the Framework Design Guidelines my man, then?
-
Well, the C# books I've run into start off with a quite Windows/VS-centric explanation of things, even when they're written for programmers, not noobs.
To be fair, most users of C# are using it on the Windows stack.
-
are the Framework Design Guidelines my man, then?
FDG is largely about why the BCL is designed the way it is, and which things they're sorry about and why. It's a good thing for anyone to read, even if they use other languages, because framework design is hard. Likewise the language spec is all about what considerations went into different parts of the syntax. It's helpful even if you only read through 2.0, just because you get a deeper understanding of why things are a particular way.
Neither of them are there to teach you C# exactly, and Windows really doesn't come into the picture much, but they help.
And I'll say it again: OpenTK in Mono is a wonderful experience if you've ever dealt with OpenGL in C before. Play around with it after reading that stuff, and you'll be in really good shape straight away.
-
Objective-C is not painful in the least. API availability is no more or less painful than on other platforms, except that, since people actually tend to update in a timely manner, you can use the newer ones. As for the corporate bureaucrats, they're everywhere, so it's not like you can escape them on Windows or Android.
Applications that could almost be done as web apps, but won't be so they can get their own icon on the phone will often be done in HTML5 using Cordova2 anyway
This tends not to happen so much.
apps that need to be done natively will have big part done in a portable way, tested on something more developer friendly
No, they tend to be tested on iOS.
-
@Bulb said:
And I really doubt Microsoft can beat it's zero cost.
They can match it easily enough; just do the same as Google. That is, free license for the OS, make money on the Marketplace.Google doesn't make money on the Play Store. They make money by collecting info and using that to sell advertising.
-
Well, you should be developing separate UIs for each platform. They have different idioms and styles. Trying to use one on both is going to provide a crappy experience for one or both platforms. Games excluded, as they generally create their own UI anyway.
-
Well, you should be developing separate UIs for each platform.
Agreed.
They have different idioms and styles.
Agreed.
Trying to use one on both is going to provide a crappy experience for one or both platforms.
Agreed.
...And yet you missed my entire point. While you should design a different UI for each platform, using XAML to do that is not a problem. What is a problem is making a really bad, half-working version of XAML be your suggested tool.
-
API availability
That's not about API availability. It is about being almost, but not completely, unlike anything else.
As for the corporate bureaucrats, they're everywhere
Yes, they are. Google are major assholes when things go wrong and you actually need to solve something with them. And main concern of the ones in Microsoft is whether you have your certification up-to-date.
so it's not like you can escape them on Windows or Android.
As a mobile developer, you don't need to talk to anybody in Google most of the time. But you need to deal with the Apple reviewers all the time.
-
@s73v3r said:
As for the corporate bureaucrats, they're everywhere
Yes, they are. Google are major assholes when things go wrong and you actually need to solve something with them. And main concern of the ones in Microsoft is whether you have your certification up-to-date.
And given our recent experience I should add that Microsoft is “successfully” following Apple lead into the asshole territory. Our WP8 porter already spent a couple of days just trying to find out what the Microsoft reviewer did not like on our new release. So it's now only Google with whom you don't have to deal regularly when developing mobile.
PS: By that I don't want to say Microsoft is worse then Apple, just that they are not good either. Our iOS release was sometimes delayed by about a month compared to the other ones due to silly complaints from Apple reviewers. On more than one occasion.
