Before reading on, you probably wonder if I’m a fanboy myself. The answer to that is both yes and no. Yes because there’s no denying the abundance of Apple made devices and solutions that enrich my daily life, both professionally and personnally. No because I have no problem recognizing the faults and strangeness to be found in the Apple eco system. But this is not about Apple in general, but the specific case of the path Apple has chosen when it comes to app third party development, approval and distribution.

Alex Payne writes on his blog:

The iPad demonstrates that if Apple is listening to these complaints, they simply don’t care. This is why I say that the iPad is a cynical thing: Apple can’t – or won’t – conceive of a future for personal computing that is both elegant and open, usable and free.

This pisses me off because it lacks perspective. If a company is manufacturing products in low-cost countries, well aware that the cheap production price comes at a high health price for the workers—and lets face it, maybe Apple is— then that’s cynical. But choosing a strategy that locks as much as possible of the inner workings of a commercial device down, simply isn’t. It might be disappointing at worst. Some argue in their own right that it’s unwise. But the bottom line is that it’s the right of any business, just as it’s the consumers right to choose not to spend their money there. The majority of western world economies are based on this general principle, and whether we like it or not, it applies to Apple as well. Complaining about cynicism in this context tells me you haven’t thought this through.

As explained by Steve and his subordinates on numerous occations, Apple believes they need control over as many aspects of their production and delivery chain as possible in order to deliver the best user experience they can. Remember, this is a belief converted to a strategy that Apple applies to the products they make and own. This has enabled them to create breakthrough products that raises the bar for everyone else in the industry and has led to real paradigm shifts in the way we work, play and communicate. HTC, Nokia/Symbian and the rest haven’t even come close in terms of sales and widespread adoption. No matter how hard you try and pick that statement apart and devaluate it, there’s no denying the fact that the sales, adoption rate and most importantly; customer satisfaction tell the same story. Apple puts this down to the very same platform model that’s been getting the worst of the tech press lately. You may argue that an equal success would have been possible if Apple had taken their combined product design, UI design and engineering wizardry and walked the open road, and you may even be proven right one day. But so far that’s been the path of their jealous competitors.

What I explain to many fresh switchers from PC to Mac is that to get the best experience you kind of have to buy into the whole eco system of the Mac. I don’t particularly like to give that advice, but it’s the truth. Apple has a vision. Where that vision deviates from many other’s is in the holistic nature of it; the fact that Apple products are designed to work best with other Apple (approved) products and to make more decisions and assumptions on the user’s behalf. To make all this possible it makes sense to control larger parts of the environment the product lives in.

As a user interface developer, I’m the middle man between the designer and the back end developers, which puts me at the center of UI/business logic debate. From this experience I know how challenging it can be to get a success from the collaboration involving just three creators that might even be used to working with each other. The designer has the vision, I may share it and execute it or break it depending on several factors. The backend guy might do either himself. Expand that example to involving, hardware, firmware, OS, software, peripherals and third party providers, and you can easily see why anyone might choose to keep this all under the same roof, within the same company culture, under the same visionary leader. You can easily say it’s hard enough as it is without providing the means for others to mess with it all they want.

I suspect that inside most of us, we like the idea of openness an sharing. I’m no different and as a Flash Developer I try to make my own contribution whenever I can. If Apple were to go 180 in the question of an open platform, I would certainly applaud them for it. Until then I’m a generally happy, relatively IT problem-free participant in the Apple eco system.

…and I’m not getting an iSlate iTablet iTampon iPad because I also think it’s an oversized iPod Touch and I don’t have a need for it. Loving my iPhone though!

EDIT: A few links to great posts on the subject:

• I Love Walled Gardens, by Rory Marinich
• jaggeree /Blog : : Why the iPad may be just what we need for Digital Inclusion
• Stephen Fry: why the Apple iPad is here to stay | The Guardian

To be honest I don’t know too much about this stuff either, but this I do know: the term “opening a port” is somewhat misleading. It took me some time to discover that it’s actually the same as “forwarding a port” or “port forwarding” as it is called in the AirPort Admin Utility for Mac. You cannot just open a port, you have to tell the router which computer on your network should receive network traffic directed to that port. That computer is identified by an IP-address, but that means entering that IP address manually, and most home networks are configured handle this automatically (by means of DHCP) and that’s likely to be the most practical solution anyway.

How do we solve this? Enter DHCP Client ID… ok, an introduction should probably end with a far sexier name than “DCHP Client ID”, but here it goes, watch:

These screenshots are in Norwegian, but the layout is the same, and I will attempt to translate.

Step 1: Open AirPort Amin Utility and select “Internet” and “DHCP”

NOTE: This requires that your AriPort is set to share a public IP address. That setting is located in the first tab under “Internet”.

At the bottom you will se something called DHCP reservations, and the list is likely to be empty, unlike mine. Below the list a +-button. Click that and this sheet appears:

Step 2: Enter a name and method for the new reserved IP address.

I chose to name it PS3, bu that’s not important. What is is that you specify DHCP Client ID as the method and click continue.

Step 3: Enter a client ID and the IP address you wish

The Client ID is important because you have to enter the same on your PlayStation. May I suggest “PS3″ for that. Next you enter an IP address. The three first numbers have been entered for you, and you have to select a number between 2 and 256. I chose 94, and if that’s not manually assigned to any other computer on your network it will work for you as well. Click “Done”.

Step 4: opening/forwarding the ports

Select “Advanced” and “Port Forwarding” and you will see something like this. Again, click the +-button below the list and this sheet appears:

Fill out the fields exactly like the screenshot, or if you chose a different IP address to be reserved for your PS3 in step 3, enter that address instead. Click “Continue”.

Here you select a name for the configuration. Again, this has no technical meaning, it’s just a description so I entered “COD4″ as an abbreviation for “Call Of Duty 4″. Pretend like the rest of the sheet isn’t there and click “Done”.

Step 5: Restart the AirPort

Restart your AirPort by clicking the “Apply”/”Update”/”Restart” (don’t know it’s actual name in English) in AirPort Admin Utility.

Step 6: Configure your PlayStation network settings

You can configure the network settings for your PS3 almost like you already have. You need to choose manual setup, but you can still use automatic detection for all settings except you DHCP Client ID, which, obviously, has to be whatever you chose in step 3. Remember my suggestion was “PS3″. After that Bob’s your father’s brother!