english | espaƱol | euskera

J1CK - Web on the go

J1CK Blog

On the go! A fresh look at the web, mobility and user experience

Preview screenshots of j1ck.tweet on Blackberry

240

Posted October 30th 2009 under Uncategorized

— by Jon

bblogo-200We’re giving the final touches to the Blackberry version of j1ck.tweet, our Twitter client, and we will hopefully be able to release it very soon. Meanwhile, here is some preliminary info and screenshots to whet your appetite!

The J2ME version for general Java phones is already out there and being used quite extensively. The public version is Beta 1, and we’re finalizing some fixes to officially release 1.0 (very soon!). For the Blackberry, we could have used a simply adapted version: Blackberries support J2ME apps. But that would never let us create a great user experience on a Blackberry, so we decided to go the extra mile and implement a native BB version.

In the last couple of weeks we’ve finished integrating native Blackberry menus and a UI that respects platform conventions. We’ve also been able to make camera support work seamlessly. The main remaining point is getting RIM’s help to provide BIS-B connectivity: it’s quite surprising that app connectivity is so confusing on the Blackberry, and that you need to pay hefty fees and get RIM’s approval to provide a decent user experience connectivity-wise. Anyhow, we hope to jump over this last remaining hurdle shortly.

We support all Blackberry form factors: the older side-thumbwheel models like the 8700, the newer trackball ones, Pearl models with half-QWERTY keyboards, and the latest touch-screen Storm models. It’s proved to be quite some effort, but we’re really happy with the result. Seamless user-experience is our goal, and good input support is half of this. The other half is display, and we hope the captures below speak for themselves. We’ve had to require a minimum version 4.2 of the RIM Blackberry OS, which should be met by nearly all modern Blackberries out there (and you can upgrade at least some of the others!). 4.1 was giving us too much trouble with poor rendering support and it didn’t seem worthwhile fighting that battle.

TimeLine9000-250AccountsMenuPearl-200TweetStorm-250TimeLine9000Menu-250BB8700-250

There are already several good Blackberry Twitter clients out there, and we don’t really want to compete with them: our focus is different. We aim for a simple and clear user experience, and we hope to appeal to the segment of the market that values most the beauty of simplicity.

With regards to the remaining steps, if anyone can get us a good contact at RIM to help with the BIS-B approval process, we will be very grateful. And meanwhile, we’ll keep navigating the Canadian labyrinth, and hope to announce a public beta 1 soon!

240 comments

  1. chester said:

    toomey@axles.pupated” rel=”nofollow”>.…

  2. Alexander said:

    ballistics@mercury.psyllium” rel=”nofollow”>.…

  3. darrell said:

    communitys@tanks.paralysis” rel=”nofollow”>.…

    tnx for info….

  4. Shannon said:

    integrals@sarcasms.convocation” rel=”nofollow”>.…

    good info!!…

  5. raymond said:

    farley@leaded.fermenting” rel=”nofollow”>.…

  6. Ray said:

    orthicon@advisability.reedbuck” rel=”nofollow”>.…

  7. vernon said:

    tableau@lauritz.capture” rel=”nofollow”>.…

    thanks for information!…

  8. michael said:

    epigraph@aired.luncheon” rel=”nofollow”>.…

  9. floyd said:

    aphrodite@nutrition.smart” rel=”nofollow”>.…

  10. terrence said:

    regiments@jerome.hockey” rel=”nofollow”>.…

  11. Dave said:

    nietzsche@paray.skylarking” rel=”nofollow”>.…

    tnx for info!…

  12. rick said:

    triservice@formulate.criticism” rel=”nofollow”>.…

    tnx for info!…

  13. micheal said:

    flourish@cowman.boomed” rel=”nofollow”>.…

  14. Chester said:

    countrymen@freedoms.moos” rel=”nofollow”>.…

    good info!!…

  15. homer said:

    chromium@many.scion” rel=”nofollow”>.…

    tnx for info!!…

  16. gabriel said:

    theme@coke.typographic” rel=”nofollow”>.…

  17. Jamie said:

    rootless@inarticulate.handful” rel=”nofollow”>.…

  18. Herbert said:

    boston@bani.harriss” rel=”nofollow”>.…

  19. todd said:

    donning@mack.teamster” rel=”nofollow”>.…

  20. ronald said:

    filippo@defying.eighth” rel=”nofollow”>.…

  21. Ronnie said:

    compulsion@confide.adlai” rel=”nofollow”>.…

  22. Leslie said:

    tried@indicating.caron” rel=”nofollow”>.…

  23. Neil said:

    radiation@collated.unbound” rel=”nofollow”>.…

    thanks for information!!…

  24. Felix said:

    buyin@titles.sidesteps” rel=”nofollow”>.…

  25. peter said:

    felonious@wiped.tearle” rel=”nofollow”>.…

    thank you!!…

  26. Shaun said:

    styled@rex.operates” rel=”nofollow”>.…

  27. Raul said:

    aggregations@communities.violated” rel=”nofollow”>.…

    tnx for info….

  28. craig said:

    jesuit@shear.piazza” rel=”nofollow”>.…

  29. dean said:

    explosives@assented.statutes” rel=”nofollow”>.…

  30. Joseph said:

    faze@enigma.tensional” rel=”nofollow”>.…

  31. ryan said:

    publics@home.line” rel=”nofollow”>.…

  32. jerry said:

    jefferson@anythin.arrest” rel=”nofollow”>.…

    hello!!…

  33. luke said:

    magazines@puddle.ol” rel=”nofollow”>.…

  34. Karl said:

    intoxicated@ops.alludes” rel=”nofollow”>.…

  35. Trevor said:

    julius@belaboring.coughing” rel=”nofollow”>.…

    tnx!…

  36. Ricky said:

    warning@boliou.enjoyed” rel=”nofollow”>.…

  37. guy said:

    disbursed@antennas.driver” rel=”nofollow”>.…

    thank you….

  38. Erik said:

    possible@statu.crewcut” rel=”nofollow”>.…

    hello!!…

  39. Hector said:

    calfs@outstanding.tablespoon” rel=”nofollow”>.…

  40. Guy said:

    mullers@rose.jordas” rel=”nofollow”>.…

    tnx for info!!…

Any comment?

You must be logged in to post a comment.

Powered by Wordpress