Web Development or SDK?


Published on

There are two distinct ways to develop applications for Apple's iPhone, the top tech gadget of the year. Programmers can choose to create optimized web applications using web languages, or to write native programs using the iPhone SDK. Rather than seeing this as an either-or proposition, developers should consider the choice a continuum and pick the right tool to create each individual program.

With iPhone web applications, programmers can enjoy all the advantages of the Internet, including ease of development and deployment, speed of updating, and off-line server access. Meanwhile, with iPhone native applications, programmers can immerse themselves in a sophisticated development environment, dig deep into an object-oriented language, and access the iPhone's built-in utilities, like its accelerometers and its GPS. This session will highlight the advantages and disadvantages of each style of programming and discuss ways to hybridize them, creating integrated projects that utilize the best of both worlds.

Published in: Technology, News & Politics
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Web Development or SDK?

  1. 1. Thoughts on Network Standards Perry Brunelli November 4th, 2008
  2. 2. Network Reliability Improved • Code upgrades no longer #1 cause of outages • Lab to test new IOS releases • Synchronization of IOS upgrades • Expertise in hardware / IOS • One throat to choke
  3. 3. Best of Breed Only a Point in Time • Notion that technologies eventually converge • Cost associated with evaluation • Cookie cutter approach scales • Shift operating expenses to capital • AANTS one example
  4. 4. Benefits of Vendor Relationship • More likely to listen to our concerns • Annual briefing at Cisco offices • Direct access to engineers and product managers • Discounts negotiated on bulk orders • Technical support on-site • Reality is that we aren’t single vendor and in many cases are best of breed: • 3750 switches, Juniper border router
  5. 5. Established Companies Not Nimble • Market leader less inclined to take risks • Less likely to embrace widely accepted standards • Small companies better suited to fill niche requirements • Need to innovate not as great
  6. 6. Standardization Not Real • Cisco model is to acquire companies • New routers have four different OS’s • SAN solution runs a different OS • Reluctance to adopt new industry open standards
  7. 7. Additional Comments • Cisco price point not always competitive • Is there value instandardizing on commodity equipment? • Example: wireless AP’s • How long do we wait for features and how much more are we willing to pay? • Example: iSCSI, Clusters • Does Arista have a more compelling price point than Cisco on 10G Ethernet gear?
  8. 8. Discussion Items • How are platform decisions made? Does this work? Should we change it? • Does the current model work? If not, how should we change it?