One-Line Verdict
furbo.org is worth following if you build for Apple platforms and want a working developer’s field notes rather than polished tutorials. Its archive since 2007 is the real asset, but the site is a personal blog, not a documentation hub, so expect uneven depth and no structured learning path.
What furbo.org Actually Is
furbo.org is the personal writing site of Craig Hockenberry, an app maker and website operator. It is not a product page or a company blog. The core of the site is a Recent Writing feed plus a deep archive going back to 2007, and an About page that links to his résumé, source code, and social profiles.
That framing matters for evaluation. A personal blog is judged differently from a reference manual. You are not buying a product; you are deciding whether one practitioner’s ongoing record is worth a slot in your reading routine. In our view, the answer depends almost entirely on whether you work in the Apple ecosystem.
The site is listed in Uslik’s Development & Programming category, and its site detail page is the quickest way to check the current feed before committing.
Strengths: What the Blog Does Well
- Specific Apple platform detail. Posts touch on concrete topics such as TipKit usage and UITabAccessory backward compatibility, which are the kind of details that rarely make it into marketing copy.
- A long, searchable archive. Writing going back to 2007 gives readers a record of how one developer’s practice changed over nearly two decades.
- Two subscription options. Readers can subscribe via RSS in XML or JSON, which suits people who prefer a feed reader over social algorithms.
- Honest range. The feed mixes technical notes with personal reflections on health and the year behind him, which keeps the voice human.
Weaknesses and Limitations
- No structure. There are no courses, learning tracks, or guided paths. You have to assemble your own reading sequence from the archive.
- Uneven depth. Because posts follow the author’s interests, some topics get one short note while others get a full essay.
- Single-author perspective. Every conclusion reflects one developer’s experience; there is no editorial board or peer review.
- No stated publishing schedule. Cadence is not guaranteed, so readers expecting weekly output may be disappointed. Current frequency needs to be confirmed on the site.
Pros and Cons at a Glance
| Pros | Cons |
|---|---|
| Hands-on Apple platform notes | No structured learning path |
| Archive dating back to 2007 | Topic coverage follows author interest |
| RSS in XML and JSON | Single-author viewpoint |
| Clear personal voice | No guaranteed publishing cadence |
Pricing and Access
furbo.org is free to read. The site materials describe RSS subscription in XML or JSON and do not present any paid tier, account, or license. No pricing page, subscription plan, or paid archive was identified in the available material.
If a paid offering or membership is introduced later, it would need to be confirmed on the official site. As of this review, there is no cost to access the writing, and there is no free-quota concept because nothing is metered.
How It Compares to Alternatives
There is no direct product equivalent, because furbo.org is a publication rather than a tool. The realistic alternatives are other reading sources:
- Official Apple developer documentation for authoritative API reference, at the cost of narrative context.
- Community forums such as those collected under Community & Forums for troubleshooting threads and second opinions.
- Other independent developer blogs for a different single-practitioner viewpoint.
Our view: furbo.org complements documentation rather than replacing it. Use the blog to learn how one experienced developer approaches a problem, then verify specifics against official references.
Who Should Follow It, and Who Should Not
Good fit: iOS and Apple platform developers who want practical notes on APIs and compatibility; readers who prefer RSS over social feeds; anyone interested in a long-running personal record of app-making practice.
Poor fit: beginners who need a sequenced curriculum; readers outside Apple development; teams looking for a maintained knowledge base with versioned documentation.
Editor Score
7.8 / 10. The score reflects strong topical specificity and a valuable archive, offset by the absence of structure, uneven coverage, and a single-author lens. It is a reading habit, not a product purchase, so the score rewards usefulness per post rather than feature completeness.
Frequently Asked Questions
Is furbo.org free to use?
Yes, the writing is free to read and no paid tier is described in the available material. Access is through the site itself or via RSS in XML or JSON. Any future paid offering would need to be confirmed on the official site.
What topics does furbo.org cover?
It covers Apple platform development and personal reflection. Technical posts include topics such as TipKit usage and UITabAccessory backward compatibility, while other entries discuss health and the year behind the author. Coverage follows the author’s interests rather than a fixed editorial plan.
Is furbo.org a good resource for beginners?
No, it is better suited to working developers. There are no courses or guided paths, and posts assume familiarity with Apple platforms. Beginners should start with official documentation and use the blog as supplementary reading once they know the basics.
How often is furbo.org updated?
The publishing schedule is not stated, so cadence should be confirmed on the site. Readers can subscribe via RSS in XML or JSON to receive new posts without checking manually. Expect irregular output rather than a fixed weekly or monthly rhythm.
Can I use furbo.org content in my own project?
Reuse terms are not specified in the available material, so check the site directly before republishing. Linking to posts and citing them is normal practice. For code snippets, verify the license attached to the linked source repository rather than assuming permission.
Final Take
furbo.org earns a place in an Apple developer’s feed reader because it shows how one practitioner actually works, including the awkward compatibility details. Treat it as field notes, not a curriculum, and pair it with official documentation. For more evaluations in this category, browse Tool Reviews on Uslik.
Comments
0No comments yet. Be the first to comment.