Xcode Project Tutorial Updates: Box2d & Template

On May 12, 2010, in Announcements, by Steffen Itterheim

If you followed my Xcode Project Tutorial or received it after signing up for my Newsletter you may have noticed that it would not compile if you added #import “box2d.h” to any of your classes. I investigated and thanks to your comments the problem was easy to fix. I wrote a Tutorial lesson detailing box2d integration issues and how to solve them.

In addition, Tim Soliday who blogs at FatFingerStudios.com went through the effort of creating a “real” Xcode Template from my Tutorial project. By “real” i mean an Xcode Template that will be added to Xcode’s “File -> New Project” list of applications so that you can choose to start with a “cocos2d Application from there. This has also been requested by readers. I added another Tutorial lesson which describes how to install Tim’s Xcode Template.

I will add Tim’s Xcode Template to the Newsletter welcome mail in a couple minutes so new Newsletter subscribers will receive it automatically! If you have already signed up for my Newsletter you’ll have it in your inbox shortly, you do not have to sign up again!

The new Projectfiles you’ll receive also contain the box2d fixes and include my free source code collection and a number of other changes. Most notably the addition of License files and folder structure that go along with it which help me and my customers to differentiate between my base source code that is only licensed to the customer vs. source code that is later fully owned by my customers. Feel free to disregard or delete these License files if you have no use for them.

Tagged with:  

Open Source is not a Feature!

On April 25, 2010, in Marketing, Mobile Business, by Steffen Itterheim

I stumbled across this AppBoy Blog Post about Android and its Market. And it reminded me of what i think when i hear people swearing by the Android: the Android is not going to rule the world. Period.

The reasons are not many but they are crucial. First, Open Source is not a Feature! I hear that very often. “Yeah but Android is Open Source, you can’t compete with that!”. Uh-huh. As a matter of fact, i do not want to compete with Open Source if that means low-quality crap. There is no quality control on the Android Market. For some this spells freedom of choice and what not. And yes, Apple has made some decisions to pull apps from the App Store that a lot of people didn’t like. But let’s not forget that 99% of iPhone OS users just don’t care. There’s still enough diversity, and it’s not like Apple has pulled the Facebook App, Twitterific, Doodle Jump or Angry Birds. Apps that people really use and like. Keep in mind that whenever Apple decides to pull an App, recently that was because of mature content while allowing a big player in that market to keep his Apps online, people talk about that because (a) they like to get upset and (b) the blogosphere and news outlets need something to talk about. In the end it’s just hot air.

Let’s get back to Android though. So it’s open source. What does that even mean? The OS itself is open source. Great for the companies who build their own devices on that software. Bad for the consumer: you still have the same problem all mobile phones have. It’s like switching from Nokia and it’s hundreds of different devices united by the Ovi Store to Android, with its hundred and more and more diverging devices and a united App Store. Where does that lead us? A huge pile of free choice no one really wants if you so will. For developers it gets increasingly harder to develop Apps that run on all Android devices and what’s more, even if you manage to support 99% of all devices right now, tomorrow there will be a new device coming out that won’t run your app. As an independent developer this is hell. You have no way of telling whether supporting a specific line of Android devices will get you a significant sales boost. So how do you calculate how much time you’ll spend on each? It’s pure guesswork. I pity Android developers.

The iPhone market itself is hard but there’s one thing you can and should put all your efforts in: Marketing. You develop for one device (well, ok make that 3) while in the meantime you figure out which websites to target, what to blog, which communities to join, where to apply for App reviews, what Press Releases to send out, etc. The code is already done, Marketing your App is the hard part. It’s the same with the Android, except that the code part with its diverging devices is just as hard to do. And it’s just not fun adapting the same app to different devices. It’s one of the things i wouldn’t mind not doing.

Most of the outspoken people who choose Android choose it because they don’t like Apple (fair enough), or they don’t like closed ecosystems and enjoy (really?) everything that has the label “Open Source” attached to it. However, they’re a minority on the Android market. Most Android users just got what they needed: a working mobile phone. They have no idea, and no clue and don’t care about Open Source. For them, the label “Open Source” has no meaning.

Tagged with:  
Page 2 of 212