May 2013 M T W T F S S « Apr 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Author Archives: Ivan Ferdelja
Moving into our new office space a few months ago turned out to be an amazing experience. Having the entire floor to ourselves with plenty of space to work, play or just rest, undoubtedly was a fresh start.
With a new office comes a new door, this time decorated by a shiny doorknob on the outside. Consequently when the fanatical developer wants to let herself in, she needs a key. With a company of 40+ this proves to be quite inconvenient, not to mention it would also make the office-manager roll her eyes. Read more
We recently developed a simple Android app that needed to run on smartphones and tablets, meaning 3-4″ phones, 7″ phonetabs with identity issues and 10″ tablets. It’s all made simple enough by the framework but some things always need a bit of tweaking.
If you own a TV, I’m sure that at some point you found yourself wishing it was loaded with software. Despite of a less enjoyable visual experience, our smartphones are already loaded with all kinds of apps. So what’s the hold up in the TV department?
Facebook SDK for Android does a pretty good job of providing Facebook support for your app. However, SDK doesen’t give you a direct way to do stuff that web users find trivial. Link sharing and link querying being two of them.
Sharing a link actually means posting a link to your wall. Keep in mind that posting a link is different from posting a status with a link attached. Posting a link brings much more value then just attaching it to a wall post, key value being the link statistics. Some of the statistics gathered for a shared link (available via Facebook Query Language) are the number of times someone shared a link, liked a link, commented on a link, etc.
Building a Blackberry app can turn out to be quite a challenge. Apparently RIM likes to treat app developers as explorers making their way through an unknown jungle. Luckily when you’ve travelled that path many times as we had, you get to be certain you’ll end up in the right place.
The place where imo RIM really gives developers a hard time is OS fragmentation and poorly documented API’s. My personal favorite is the very common note found in RIM javadoc stating that „this method is invoked by the underlying framework and might not work as expected“. Surprised? I was. So yes, we all know Blackberry development has its issues. But then again, which platform doesn’t?