Manning has now released Chapter 2 as a free sample from our book
"iPhone in Action: Introduction to Web and SDK Development" as a PDF
at http://www.manning-source.com/books/callen/callen_meapch1-2.pdf#page=16

The title of this chapter is "Web Development or the SDK?"

For more information on the book see http://www.manning.com/callen --
there is currently a 50% discount for early purchasers.

Excerpt:

This chapter covers:

* Delineating the two types of iPhone Development

* Addressing them each as being valuable in its own right

There are two different ways that you can develop for the iPhone. On
the one hand, you can write web pages for Mobile Safari, using HTML,
JavaScript and your favorite dynamic language. On the other hand, you
can write native applications to run directly on the iPhone, using
Objective-C and the iPhone SDK.

It is our strong belief that each of these programming methods has its
own place, and that you should always ensure that you're using the
correct one before you get started with any iPhone project.

We're well aware that many of you are coming to this book from one of
two directions. Either you're a web developer who wants to learn how
optimize his web pages for viewing on the iPhone, or else you're a
programmer who wants to extend his C programming experience to the
iPhone. We welcome you both, and we're certain that you'll each find a
great introduction to your style of programming on the iPhone herein.

However, we also encourage you both to read the entire book, because
we believe that by understanding—and using—the entire continuum of
iPhone programming you'll literally get twice as much out of the
experience. For the web developer, we're going to tell you everything
you need to know about the specifics of iPhone programming, including
digging into some web features that you're probably not familiar with,
such as iUI and Canvas. However, we hope you'll keep reading from
there, as our material on the SDK is all quite introductory, and even
if you've never worked with a compiled programming language, we think
you can use this book to bootstrap yourself up to SDK programming.

Chapter 8 is the foundation of this. It'll provide you with the basis
of how a compiled programming language differs from the PHP, Perl, or
Ruby on Rails that you might be familiar with. Starting from there you
should be able to learn the same lessons as a more experienced C
programmer when we dive into the SDK itself.

For the SDK programmer, we're going to provide you with a complete
introduction to all of the SDK's coolest features, including all of
the unique iPhone features that we've already touched upon, such as
its GPS, its accelerometers, and its unique input device. However, we
hope you won't consider SDK programming as the be-all and end-all of
iPhone software. We feel that there are genuinely places where web
development is a better choice.

We'll argue the reasons that you might select web development over SDK
right here, in this chapter. Even if you're familiar with web
development already, we invite you to next skim through the web
chapters, because we end each with a look at the lessons that web
development can teach us about the iPhone as a whole. Finally, toward
the end of the book, we're going to look at how web protocols can be
integrated directly with your SDK work using a client-server
methodology.

Generally, no matter what type of programmer you are, you should think
of this book as a toolbox. It's divided into two large compartments,
but every tool within has the same goal: creating great iPhone
programs. You just need to make sure that you're always using the
right tool for the job at hand.

-- Christopher Allen

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iPhoneWebDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/iphonewebdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to