Category Archives: wireless networks

Aakash: A Disruptive Innovation in the Truest Sense

Posted on by
3

Much has been, and will be, written about the Aakash tablet.

[With apologies for the situational monsoonal imagery …] As I awash myself in Aakash, I am particularly taken by:

  • The order of magnitude reduction in price point. With a stated cost of about $50, marked-up prices are still close to an order of magnitude more affordable than the incumbent offerings (e.g., the iPad, Android-based tablets, etc.). Even Amazon’s Kindle Fire is 2-3 times more expensive.
  • The adoption of Android as the innovation platform. I take this as yet another data point (YADP) in firmly establishing Android as the leading future proofed platform for innovation in the mobile-computing space. As Aakash solidly demonstrates, it’s about the all-inclusive collaboration that can occur when organizational boundaries are made redundant through use of an open platform for innovation. These dynamics just aren’t the same as those that would be achieved by embracing proprietary platforms (e.g., Apple’s iOS, RIM QNX-based O/S, etc.).
  • The Indian origin. It took MIT Being Digital, in the meatspace personage of Nicholas Negroponte, to hatch the One Laptop Per Child initiative. In the case of Aakash, this is grass-roots innovation that has Grameen Bank like possibilities.
While some get distracted comparing/contrasting tech specs, the significant impact of Aakash is that it is a disruptive innovation in the truest sense:
“An innovation that is disruptive allows a whole new population of consumers access to a product or service that was historically only accessible to consumers with a lot of money or a lot of skill.  Characteristics of disruptive businesses, at least in their initial stages, can include:  lower gross margins, smaller target markets, and simpler products and services that may not appear as attractive as existing solutions when compared against traditional performance metrics.”
I am certainly looking forward to seeing this evolve!

Disclaimers:
  • Like Aakash, I am of Indian origin. My Indian origin, however, is somewhat diluted by some English origin – making me an Anglo-Indian. Regardless, my own origin may play some role in my gushing exuberance for Aakash – and hence the need for this disclaimer.
  • I am the owner of a Motorola Xoom, but not an iPad. This may mean I am somewhat predisposed towards the Android platform.
Feel free to chime in with your thoughts on Aakash by commenting on this post.

Under Review: Packt’s “Funambol Mobile Open Source”

Posted on by
Reply

I’m currently reading Packt’s “Funambol Mobile Open Source”. Written by the creator of the project, Stefano Fornari, this book covers a solution for the synchronization of data between multiple devices. A sample chapter is available.

Stay tuned.

Blended Learning Panel

Posted on by
2

York University’s Institute for Research on Learning Technologies is sponsoring a panel discussion on blended learning:

“A recent workplace survey reported by Brandon Hall Publishing (2008) indicates that employing a mix of web-technologies with face-to-face learning is more effective than either e-learning or face-to-face instructional approaches alone. To explore the use and potential of “blended learning” further, please join us for a panel discussion featuring experts from various fields …”

This event has been re-scheduled for April 2, 2009 at 12:15 pm in TEL 1009 at York’s Keele Campus. I anticipate a lively and interesting discussion!

(Please check the IRLT Web site for the latest updates on the event.)

Synced-Data Applications: The Bastard Child of Convergence

Posted on by
Reply

At the Search Engine Strategies Conference in August 2006, in an informal conversation, Google CEO Eric Schmidt stated:

What’s interesting [now] is that there is an emergent new model, and you all are here because you are part of that new model. I don’t think people have really understood how big this opportunity really is. It starts with the premise that the data services and architecture should be on servers. We call it cloud computing – they should be in a “cloud” somewhere. And that if you have the right kind of browser or the right kind of access, it doesn’t matter whether you have a PC or a Mac or a mobile phone or a BlackBerry or what have you – or new devices still to be developed – you can get access to the cloud. There are a number of companies that have benefited from that. Obviously, Google, Yahoo!, eBay, Amazon come to mind. The computation and the data and so forth are in the servers.

My interpretation of cloud computing is summarized in the following figure.


Yesterday, I introduced the concept of Synced-Data Applications (SDAs). SDAs are summarized in the following figure.


SDAs owe their existence to the convergence of the cloud and the desktop/handheld.

Synced-Data Applications: The Future of End-User Software?

Posted on by
1

I recently asked: Is desktop software is dead?

Increasingly, I am of the opinion that desktop software is well on its way to extinction.

In its place, Synced-Data Applications (SDAs) have emerged.

One of the best examples I’ve recently run across is Evernote. Native Evernote applications exist for desktops (as well as handhelds) and for the cloud (e.g., via a Web browser). Your data is replicated between the cloud (in this example, Evernote’s Webstores) and your desktop(s)/handheld(s). Synced-Data Applications.

And with Google Gears, Google Docs has also entered the SDA software paradigm.

With SDAs, it’s not just about the cloud, and it’s not just about the desktop/handheld. It’s all about the convergence that this software paradigm brings.

A revised version of the figure I shared in the previous post on this thread is included below.

Once again, it emphasizes that interest is focused on the convergence between the isolated realm of the desktop/handheld on the one hand, and the cloud (I previously referred to this as the network) on the other.

It’s much, much less about commercial versus Open Source software. And yes, I remain unaware of SDA examples that live purely in the Open Source realm …

Introducing Jott for BlackBerry

Posted on by
Reply

I just learned about Jott for BlackBerry:

We have a lot of happy Blackberry customers at Jott, and Jott for BlackBerry is the ultimate BlackBerry download. It is a simple, but very powerful tool that will let you reply to emails on your BlackBerry just using your voice – either speaking directly into your BlackBerry, or while wearing a Bluetooth headset. It is seamlessly integrated into the email application you already use, and is a huge leap forward for BlackBerry lovers in three ways: first, it is 3-5 times faster than ‘thumbing’ text; two, you won’t be known for sending just terse replies because you don’t want to thumb type out a normal email message; and three, you will be safer because you won’t have to take your eyes off the road.*
(*Jott does NOT encourage messaging while driving).

Jott for Blackberry makes an already awesome device even better.

The following is the body of a reply I just created:

Thanks for sharing this interesting service with me. It's definitely something that I'm interested in investigating and it's my intention to follow up very very soon. Thanks very much. Bye for now.

Sent with my voice via Jott for Blackberry ~ http://jott.com/bb

To listen: http://www.jott.com/show.aspx?id=e4eb3151-9007-448c-bd73-7de70ecc4766

In this example, the transcription quality was excellent. Note that the recipient is advised that the response was Jott’ed, and has the option of listening to the original audio recording. Nice!

Although I’m only at the testing stage, I expect to make extensive use of Jott for BlackBerry!

Note to Jott and Google: Please enable Jott for BlackBerry in the GMail for BlackBerry application.

sync blackberry contacts with gmail: Problem Solved!

Posted on by
40

Update (February 10, 2009): See Sync Google Calendar and Gmail Contacts with Your BlackBerry for a recent How To guide to the Google Sync for the BlackBerry solution.

In just over fourteen months, one of my posts has received almost 19% of the views for my entire blog.

There is no other post that even comes close.
And to make matters more interesting, the post was written in response to my blog’s search stats. People consistently entered strings along the lines “sync blackberry contacts with gmail” and arrived here.
Frankly, all of this attention made me uneasy.
Why?
Because I really didn’t have much to offer on the topic.
But please don’t think that I didn’t give this information (not data!) some thought.
Honestly, dear reader, I confess I even pondered how I might arrive at a solution that might monetize this 19% for personal gain. Let’s face it, 19% of more than 60K hits translates potentially to more than 11K customers. Ka-ching! I am in disgrace.
Luckily I didn’t waste my time.
Waste, you gasp. Yes, waste.
You see, the fine folks at Google have delivered a solution.
It’s all in the GMail contact manager. This new addition to the GMail client for the BlackBerry solves the problem.
How?
If you have a contact for which you’ve entered phone numbers, these numbers appear when you click on the contact name to view their details. But that’s just the beginning. The phone numbers appear as clickable links. When you click on one of them, you automagically invoke the BlackBerry’s phone capability. (You may have forgotten that your BlackBerry actually allows you to call people as well.) Note that the first time you do this, you’ll need to approve some new settings.
Of course, you can email contacts as well.
Problem solved.
Please read my other posts!
If truth be told, this should be regarded as a great beginning.
Here’s why:
  • Read-only access – You can’t enter contact information from the GMail client on the BlackBerry. In time, we’ll want this. Like tomorrow!
  • Online-access only – You need your contacts when you’re off line? Like when you’re on an airplane? Until this client includes Google Gears functionality or equivalent, you’re out of luck here. I think I can live with that. For now. Because ultimately I would appreciate the ability to compose email when I’m off line. I do that frequently with the BlackBerry’s built-in mail client.
  • Contacts in too many places – Fragmenting contacts between your Google ‘verse and enterprise messaging platform (e.g., Microsoft Exchange, IBM Lotus Notes, etc.) has some disadvantages. However, as I’ve learned directly on the heels of personal experience, there are times when it’s wise to have some separation between our personal and corporate selves …

This gives me a lot of what I was looking for.

How about you?

GMail on Your BlackBerry: Latest Client Offers Significant Featur

Posted on by
9

A few days ago I upgraded to version 1.5.1.1090 of the GMail client for my BlackBerry 8130. (This is a native, stand-alone, J2ME client application. In other words, it does not require a Web browser.) Previously, and for the past few months, I’ve been using version 1.1.x of this same client. 

The download and installation went very smoothly. One surprise, however, was the need for a reboot of the BlackBerry to complete the installation of the client. I don’t recall that need with previous releases. I can only suppose that this requirement is necessary to enable the deeper integration of the GMail client with the BlackBerry platform.
And that’s a good segue … What’s new? Well: 
  • Contact manager – This is the most significant feature/functionality enhancement. On opening the contact manager, a display of those with whom you interact with the most is presented. There’s also a search functionality that allows you to rapidly retrieve any of your contacts in the familiar way. And of course, should you wish, you can list all of your contacts. Once you’ve selected a contact from the “Most Contacted” list or via search, your contact’s details are presented. Just below the contact details is a link that allows you to display recent conversations with the identified contact. Very powerful. Very Google. Very nice! All of this means that you can initiate a new conversation or pick up on an existing one from the contact manager.  
  • Notification – The notification capability is also a significant enhancement in my estimation. What this means is that an icon resembling a bottle cap appears over top of the GMail client icon to indicate the arrival of new mail. This capability is integrated with your BlackBerry profile so you can associate in and out-of-holster behaviors to signal the arrival of new mail. The only thing missing now is the summary icon that is displayed by other applications in the upper-right corner of the BlackBerry’s screen. This capability is enabled via a new setting; select “More”, then “Settings” before placing a check mark against the notification option. There are a few more settings that are new to me – one allows for larger fonts, while the other allows for the “Sent from my mobile device” tag line. 
  • Finish Later – In the event that you are unable to finish composing a message, this version allows you to finish composition later. Note however, that only one draft can be saved. This is a welcome addition that I found myself pining for in previous releases.
As far as I can tell, that summarizes the features that I found new in this release. Based on a few days’ worth of experience, the implementation appears solid and performs well, making the upgrade highly worthwhile.
You can grab the GMail client for your mobile device by pointing the device’s Web browser at gmail.com/app. See Google Mobile GMail  for the details.
If you’re using Google Apps for Your Domain (GAFYD), point your mobile device’s Web browser at http://m.google.com/a. See the Google Apps page for more.
If you want to see what I’ve written previously about the GMail client for the BlackBerry click here.

 

BlackBerry Rules the Back Office – For Now …

Posted on by
1

I’ve had a BlackBerry 8830 for a few months now. And I must admit, I’m getting over my iPhone envy. (iPhone’s still aren’t officially available in Canada!) The 8830 has the tactile keypad I’ve grown to love, a (two-dimensional) trackball in place of a (one-dimensional) thumbwheel, GPS-based mapping, etc. This means that built-in WiFi is about the only capability for which I find myself wanting.

But enough about the client-side device (CSD).
So much of the value delivered to the CSD is because of what’s in the back office – behind the scenes, as it were.
In writing a book review on BlackBerry Enterprise Server (BES) installation and administration, I was reminded of this aspect on the ongoing BlackBerry vs. iPhone battle.
What’s in the BlackBerry back office?
Allow me to itemize:
  • Integration – The BES integrates the CSD with the enterprise messaging platform (e.g., Microsoft Exchange, IBM Lotus Notes, etc.) and the rest of RIM’s BlackBerry universe. In addition to email and calendaring, this has the potential to include instant messaging (e.g., MSN, IBM Lotus Sametime, etc.) and more.
  • Security – Because the BES provides a single locus of control (the BlackBerry domain), it can and has been leveraged extensively to deliver an industry leading environment for end-to-end security. Encryption, authentication, plus six levels for administrative roles, are all present.
  • Policies  – To quote from my review:

The BES ships with over 200 policies that can be applied variously to users, groups and devices … The ability to administer users, groups and devices with respect to policies (including software), from a single point of control (i.e., the BES server), speaks volumes to the appeal and value that this offering can deliver to corporate enterprise environments. 

  • Provisioning – The BES facilitates provisioning of users, groups, devices as well as associated software. Software can even be bundled and targeted to specific CSDs.
The back office supporting the iPhone has a long, long way to go to catch up with all of this – if that’s even a plan that Apple has.
In fact, a far greater threat to the back-office portion of RIM’s BlackBerry universe is the ecosystem developing around Google Android.

Book Review: BlackBerry Enterprise Server for Microsoft Exchange

Posted on by
7

Packt Publishing claims its

… unique business model allows [them] to bring [us] more focused information, giving [us] more of what [we] need to know, and less of what [we] don’t.  

If Desai & Renfroe’s BlackBerry Enterprise Server for Microsoft Exchange: Installation and Administration is any indication, Packt actually lives up to its claim. In just 172 pages, Desai & Renfroe achieve an enviable balance between being concise and being comprehensive. This statement applies as much to what the authors have written, as to their choice of what to illustrate. Specifically:

  • Chapter 1 places the BlackBerry Enterprise Server (BES) in the broader context of Research In Motion’s (RIM) BlackBerry universe. In addition to itemizing relevant components, an introduction to the BlackBerry’s push model, security and Internet connectivity is provided. 
  • Though brief, Chapter 2 runs deep in addressing BES architecture and implementation planning. For example, we learn that the BES employs a modular architecture comprising over a dozen components. After succinctly enumerating the components and their function, BES requirements and prerequisites are identified. In addition to hardware and software requirements, recommendations are made with respect to networking your BES (e.g., firewall and/or proxy considerations) and providing it with a database. Easy to gloss over on first read are thoughtful recommendations on sizing the BES (including pointers to resources from RIM) and the database for the anticipated user load. 
  • Before BES components can be installed and enabled, the messaging environment and database server need to be configured. This is the subject of Chapter 3. Both local and remote database instances receive attention. Because each step is well illustrated, the book delivers on its intended purpose of serving as a solution guide.
  • The installation of the BES is a multistep process enabled via a wizard. As in the previous chapter, in Chapter 4 the authors guide the reader through this process making appropriate use of illustrations. They interject appropriate commentary, and are clear on out-of-scope topics. The early emphasis on delineating BES architecture (Chapter 1) is realized as the authors transition the reader through the BES installation. 
  • Of course, installing the BES is just the beginning, and therefore the next few chapters focus on the additional tasks required to operationally deliver this service to its users. After introducing the six permissible levels of administrative role on the BES, attention shifts in Chapter 5 to the matter of provisioning users, groups and devices. And with respect to devices, wireline and wireless options for provisioning are given consideration. 
  • The BES ships with over 200 policies that can be applied variously to users, groups and devices. Also covered in Chapter 6 is the topic of provisioning software from RIM and third parties. Of particular value is the authors’ example of a software bundle targeted to a particular BlackBerry model. The ability to administer users, groups and devices with respect to policies (including software), from a single point of control (i.e., the BES server), speaks volumes to the appeal and value that this offering can deliver to corporate enterprise environments. This Chapter’s treatment of policies and software provisioning serves as an excellent introduction to topics BES administrators will return to repeatedly, and likely with increasing degrees of sophistication. 
  • Unlike many of the other chapters, Chapter 7 provides only an overview of multitiered administration – i.e., properties and tasks relating to users, groups, (BlackBerry) domains and servers. This enumeration of possibilities, presented in context, works effectively. 
  • A deeper discussion on security is the focus of the first part of the final chapter (Chapter 8). Encryption and authorization, both of which receive detailed consideration, amplify the value of the BES and its context in the overall BlackBerry universe for corporate enterprises. An unanticipated treatment of disaster recovery closes Chapter 8. In sufficient detail to enable a solution, the authors discuss in turn the measures needed to ensure that both the server (the BES) and its data (housed by the BES’s local or remote database) are readied for a disaster situation. 

 

Although Desai and Renfroe’s BES book unapologetically targets the Microsoft Exchange environment, its value is not limited here. Those working in other environments, and those interested in learning more about BES’s place in the BlackBerry universe, will almost certainly derive value from this book. Because the book is clear and concise, yet surprisingly complete and well-organized, it is likely to be well-thumbed by BES administrators of varying expertise.  

With the possible exception of a concluding chapter, page, paragraph or even sentence(!), to provide some sense of closure to the book, I am at a loss to report any omissions, oversights or errors. And although they might be better suited for a follow-on contribution of some kind, additional discussion might be given to topics such as performance and scalability (e.g., of local versus remote databases), the mapping of BlackBerry domains to organizational units, and/or improved degrees of DR.

Even though the book I reviewed was a complimentary copy provided by the publisher, I would happily pay for my own copy, and heartily recommend this book to others having interest in BES installation and administration.