Episode 51 – Twitter, You’re Holding It Wrong

This week we discuss all kinds of social networking tools prompted by Twitter’s report on slowing user growth. We discuss how the various popular social networking tools are used by the general public and it skews differently for those of us in the tech sector.
Picks: pttrns.com, bloc app, App Icon Template. Tim discusses Bed Debugging in the aftershow.

Before and After heat treating the house to 190°F

Episode 51 Show Notes:

Episode 51 Picks:

Episode 17 – Why Did the Chicken Crossy the Road?

This week we follow up on hiring the best iOS developers. We delve into changes to Twitter’s API and how they are holding back deep search features. Jaime steals Aaron’s pick with Crossy Road. Aaron’s pick is to introduce part one of a look into Apple’s TestFlight implementation through iTunes Connect. Tim’s pick is Screeny, an app that lets developers cull screenshots stored on the iPhone, the (RED) campaign and Monument Valley’s additional (RED) chapter. Tim also discusses the updated 3rd Edition of iOS 6 By Tutorials – covering the features added to iOS 6, updated for Xcode 6 and iOS 8.

Screen Shot 2014-11-26 at 10.07.02 PM

The picture Tim was trying to send

Episode 17 Notes

We Hire the Best
Hiring the Top 1%
New Twitter search API won’t be available to third-party clients
Build & Analyze – California Knife in Your Back
Twitterific 5 for Mac… the first casualty
Library of Congress Is Archiving All Of America’s Tweets
What the Library of Congress Plans to Do With All Your Tweets
WatchKit Resources site curated by FoS Brian Gilham
https://www.udemy.com

Episode 16 Picks

Crossy Road
Screeny
Monument Valley
iOS 6 by Tutorials Third Edition

Listen or Subscribe on iTunes

Listen or Subscribe on FeedBurner

Writing apps to work with twitter – avoid 403 error.

I’ve been working on some social networking apps, by following examples. It’s really frustrating to find that the authors haven’t tested their code, before, during or after publishing. So here are a couple of things I’ve found.

If you are attempting to post or read from Twitter’s API, you must use HTTPS.

Hopefully, this will save you some head scratching.