On component discoverability...

Here at mobile[foo], we've been playing with some iOS app development in the last couple of months, and something keeps coming back to us: there's loads of really cool stuff out there, and loads of people who haven't managed to find it yet. Ourselves very much included: I did far more work on Stacks & Heaps that's been done by others, much better than me, many times before.

There's some great examples of Open Source components: enormego's Twitter-style "pull-to-refresh" control, which has itself now made its way into the equally cool Three20 project; Matt Gemmell's awesome MGSplitViewController enhancement on the native iPad component, and even the small but highly-effective Appriater library that prompts your users to leave you a review on the App Store some time before they uninstall it.

However, as someone starting out, or even perhaps more experienced, in mobile app development, finding these libraries can be a problem. There's often a willing answer on StackOverflow or similar, and even a thread listing a few of the more obvious components, but that's not an efficient way of keeping track of such things.

What we're aiming to provide is a way of letting you discover the amazing wealth of content that's out there, quickly, effectively, and easily. It doesn't need to be limited to OSS, though there's some great Open Source content, but if you've got a commercially available component or library, we'd love to hear from you as well.

What now? Tell us we're mad, watch this space, or follow us on Twitter...

Contributors

Tags

Archive

2011 (25)