Initially, iPhone SDK development was largely done in isolation-- the SDK doesn't support dynamic frameworks and making a static library was not obvious if you weren't already used to writing code for the Mac. As time has progressed, a number of people have published frameworks, libraries, or just plain code that does a specific task, does it well, and is intended to be integrated into other iPhone applications.

There's a number of such projects that I've found useful and, in some respects, indispensable:

PLCrashReporter ( http://code.google.com/p/plcrashreporter/ ): a library that captures application crashes so that you can then do something with them. While Apple now provides crash reports to you via iTunes connect, I use this and get immediate delivery of problems almost as they happen. In most cases, by using this, I've already been notified of a problem, fixed it, and have uploaded the corrected application before the crashes show up in iTunes connect.

JSON Framework ( http://code.google.com/p/json-framework/ ): a JSON library for Objective-C. Very useful if you're talking to a server.

ASIHTTPRequest ( http://allseeing-i.com/ASIHTTPRequest/ ): a CFNetwork based framework that makes dealing with RESTful web services easy.

Three20 ( http://github.com/joehewitt/three20/tree/master ): A framework by Joe Hewitt that provides many of the user interface components used by the current iPhone Facebook application. It's biggest shortcomings are the lack of documentation and the tight coupling between the various components.

ObjectiveResource ( http://iphoneonrails.com/ ): serialization to/from a Ruby on Rails based application using Rails standard web-services.

LLamaSettings ( http://code.google.com/p/llamasettings/ ): provides a relatively easy way of making standard looking Settings screens.

KCalendar ( http://code.google.com/p/kcalendar-iphone/ ): a simple calendar view, modeled after the built in calendar application.

What other such frameworks are you using?

Views: 23

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

Podcast: Building the Muscles for Critical Thinking

In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Dannielle Pearson about the importance of critical thinking in technology.

By Dannielle Pearson

.NET Aspire Preview 6: Enhanced Security and Testing, New Features, and More

This week Microsoft released Preview 6 of the .NET Aspire project. Significant changes have been implemented to enhance the security and reliability of the platform. This release, version 8.0.0-preview.6.24214.1, introduces several noteworthy additions, like changes related to templates, components, dashboard, testing and more.

By Almir Vuk

Presentation: Sleeping at Scale - Delivering 10k Timers per Second per Node with Rust, Tokio, Kafka, and Scylla

Lily Mara, Hunter Laine walk through the design of a system, its performance characteristics, and how they scaled it.

By Lily Mara, Hunter Laine

Article: Is Your Test Suite Brittle? Maybe It’s Too DRY

One important design principle in software development is DRY – Don’t Repeat Yourself. However, when DRY is applied to test code, it can cause the test suite to become brittle — difficult to understand, maintain, and change. In this article, I will present some indications that a test suite is brittle, guidelines to follow when reducing duplication in tests, and better ways to DRY up tests.

By Kimberly Hendrick

Allegro Reduces Kafka Producer Latency Outliers by 82% After Switching to XFS

Allegro experimented with different performance optimization options to improve Apache Kafka producer tail latency and eventually switched all its clusters to the XFS filesystem. The company used Kafka protocol sniffing, JVM profiling, and eBPF, which proved instrumental in identifying and eliminating performance bottlenecks.

By Rafal Gancarz

© 2024   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service