iOS (with a bit of Android experience) and quite a bit of experience (albeit, on my own projects) in Ruby (mostly the Sinatra framework) and PHP.
I have a gap of a few weeks before starting my placement year (I'm a Computer Science student), but I likely will be looking for projects even when that starts.
It seems to me to be a very bad business decision to decide to write a framework first, before delivering on your core product.
As the deadlines have ended up slipping, they have ended up with a set of very defensive posts about why they haven't yet delivered.
I don't see why you would jeopardize (that might be a bit of a strong word, but I'm sure they haven't done amazingly in sales in the last few months compared to what they had been) your business by attempting something far more complex when your product was already behind others in the marketplace.
There's no reason why they couldn't have gotten cloud syncing working just for them, then rolling out the code into a framework later on. That seems to be the smarter way to go about doing it - not writing a series of defensive posts saying that it's so hard.
"It seems to me to be a very bad business decision to decide to write a framework first, before delivering on your core product."
But they have delivered on their core product (Things.app)...and an expansion of it (Things for iPhone, etc.).
Don't get me wrong...they could be overengineering it (I don't know their user base that well), but it seems that they might be taking the Blizzard approach to things (we're not giving a release date...it'll be done when it's done).
For someone looking only at the tips, this is sadly very unfriendly. Basically, you need to click or press more than 300 times on your keyboard to go through. This cannot be used as a reference even so some stuff were interesting (I gave up at slide 84). I welcome a reformatting as a cheat sheet by a courageous reader :)
Pick up an Arduino, or one of it's derivatives (like Netduino). Then span out. Once you've gotten 'in', you'll soon find other interesting platforms to develop on.
It's not simply businesses that are effected. Overall, it is young people who use BlackBerry's in the UAE.
The two carriers (Etisalat & Du) have pushed them heavily here. They allow young people to talk to each other without actually talking - which would be taboo.
If you go anywhere in the UAE, nearly all you can see is BlackBerry's. People spend more than half of their time messaging each other, email or otherwise.
I think the Gulf states are trying to apply their power to make RIM play their game. The states will succeed if RIM thinks it's a worthwhile market to stay in.
Which are generally MIT/BSD variants.