Topic: iPhone SDK

iPad: Instant Reaction to Apple’s Tablet Event

Bernhard Kappe, Wednesday, January 27, 2010 @ 3:09 pm

I just finished looking at a couple of live blogs on Apple's big iPad event, flipping back and forth between Macworld and Ubergizmo's coverage.

While initial reaction has been all over the map, mine is overwhelmingly positive. I think they hit a grand slam.

Here's why:

1. There are lots of reasons why a tablet is a better mobile device than a laptop or a netbook.
2. The price is right (Starts at $499, goes to $829)
3. The data plans are right (Wifi, 3G $14.95 to $29.95 for data plan coverage from AT&T, use at all wifi hotspots, no contract.)
4. iWork for $30. Web browsing, photos, vidoes, reading, games, email, word processing, spreadsheets and presentations - that's 95% of what 90% of people do with a computer.
5. Dock and Keyboard. Use it like a desktop, if you must.
6. iPhone and iPod Touch software works on it now, the SDK (iPhone OS) and emulator are released the same day, and units will ship in 60 days. That means iPhone developers like us will be pushing out new versions of those 100,000 apps as well as brand new apps out there as fast as we can design and code.
7. The app store model makes installing new apps a one click affair. I don't get any "Honey, can you help me" shouts from my wife with the iPhone, and I wont get them with the iPad either (especially since it doesn't have a camera;-)

In short, this is great news for those people yearning to trade away technical complexity for vastly increased simplicity and ease of use.

Sure there are things that a lot of people (smart, tech savvy analysts and developers all) will bemoan* and think are missing, but the same thing could be said of the iPhone. It's Apple's way (only release it if it kicks ass and makes them money) it works, and it will work here as well.

* I of course was hoping for front facing video camera for video phone support.

• Digg
• Reddit
• del.icio.us

Comments (0)

rich internet apps

Writing Your Own Protocol With NSURLProtocol

Ivan Moscoso, Saturday, June 27, 2009 @ 8:39 pm

I have a native iPhone application in development which requires me to interact with a server that uses a stateful protocol over a persistent connection to transfer messages over the wire. This is definitely not a trivial application to write, even though the UI itself is very simple.

The Problem

Stateful protocols and persistent connections are often interrelated, but not by design. My first problem was to divide the original problem in two: how to manage the persistent connection, and how to handle the underlying protocol so that the stateful aspects did not bubble up throughout the UI.

Continue reading »

• Digg
• Reddit
• del.icio.us

Comments (0)

software development best practices

iPhone SDK and the Audacity of Patience

Ivan Moscoso, Wednesday, July 9, 2008 @ 11:43 pm

You might be wondering what I've been up to lately.

I have been working with the iPhone SDK (the better half of three months now), and have been having more than a bit of fun.  Not only have I had to re-familiarize myself with Objective-C and the Cocoa APIs, but I have started thinking more seriously about what it means to write great mobile applications.  All of this led me to wonder about the experiences of other non-Cocoa developers (after all, there is a lot of ground to cover).  Not surprisingly, while there are a few early adopters who feel so out of their element that they are tempted to write it off, I'm confident that there are others who are like me-- psyched up and ready to go.

Unfortunately I can't get into specifics of my experience so far while holding to the NDA, other than to say that learning anything new requires patience, but ultimately if you are experienced enough, the lessons you already know about good design will move you much farther along than any choice of IDE or language or API.
Continue reading »

• Digg
• Reddit
• del.icio.us

Comments (1)

Software Development