John Wargo

Home
JohnWargo.com
What were they thinking... PDF Print E-mail
Wednesday, 09 December 2009 06:21
AddThis Social Bookmark Button

For our Lotusphere presentation in January, Rob Wunderlich and I started talking about how to approach our topic about mobile web development. One of the things that came up was an agreement that a lot of developers, while they know all about web development, didn't think of the ramifications of their decisions as they mobilized their sites. Even though the mobile browser supports most of the web development standards, it doesn't mean you should make use of them. Also, even though you know how to build a site for a desktop browser, doesn't mean you should do the same thing for the mobile user.

We decided then that the underlying theme for our session was going to be 'What were they thinking' and in preparation for that I have started collecting examples of bad (bad, very bad) things that mobile developers do that makes life hard for mobile users. As I collect these things, I'll start posting them to the site and see where I can take this.

The first example for this series is is shown below. I am at a hotel attending some sales training (yep, I'm a sales guy now) provided by my employer and tried to connect to the hotel's wireless network to do some work. My BlackBerry Storm 9700 was smart enough to recognize that I was on a hotspot network, so immediately launched the hotspot browser so I could login to the access point before going on to do my work. When I looked at the page, I noticed something that I thought I'd share with you as the first rule in the 'what were they thinking' series.

Take a look at the following image:

iBAHN Login Page

The site gave me an easy way to select my language that didn't consume too much screen real estate (always a good thing). Imagine how much harder it would have been to use if there was a big list of languages or a drop-down list containing the list of supported languages?

Where the developer went wrong was in the way he (or she) used the radio button. Whenever you present a radio button to a mobile user and there's only one item in the list, you make them do extra work to select that tiny little button before clicking next. The smart developer will detect how many items there are in the list and either remove the choice all together or, if you're going to put a single item in a radio button list, pre-select the only available option. Don't make the user make the selection if there's no possible other option for them to use. It just doesn't make sense to make the user do that extra work when it's not necessary. 

I'm a little older and I'm starting to have trouble reading mobile device screens without my glasses, so when I was first presented with this page I immediately clicked the next button and didn't think about the radio button.Of course the page errored out and I had to go back and pay close attention to what I was doing - but this wasn't a good use of my time.

If you're building a site like this, please think about the impact of these types of things on your user. There's no reason to force a selection when there's really nothing to select.  Make sense?  Implementing this in dynamic environments like PHP or Domino is really, really simple - just a simple if statement with two different HTML outputs depending on the number of options in the list.

 
Speaking at Lotusphere 2010 PDF Print E-mail
Wednesday, 02 December 2009 15:23
AddThis Social Bookmark Button

I’m excited to announce that I’ve been selected to present two sessions at Lotusphere 2010.

Rob Wunderlich and I are presenting a session entitled: ‘Delivering IBM Lotus Domino to Mobile Devices: Top 10 Mobile Browser Dev Tricks.’ The topic stems from some sessions Rob’s done at previous Lotuspheres and some sessions I’ve done at the View Domino Administrator/Developer Conference. It’s designed to highlight the trips and tricks of building Domino browser based application for mobile phones and smartphones. There’s so many things web developers need to worry about when working with mobile devices – we’re going to try to lay it all out for people who attend the session.

Rob and I have been working on the outline for the session and it’s really beginning to come together. I’ve known Rob for a long time and he and I both have interesting perspectives to bring to the session. We’re having some interesting discussions about some common misconceptions and things that need to be taken into account when building mobile web applications.

Here's a link to the session abstract:

https://www-950.ibm.com/events/wwe/lotus/lsph2010.nsf/sessionabstract?openform&sessionid=BP212

The other session I’m doing is called ‘Beyond the Mobile Browser – Building Rich Mobile Applications for Domino.’ It’s really an extension of the first session. In this one, I’m going to demonstrate how to build several mobile rich client applications that talk to a Domino Database. The assumption here is that although the browser is cool and all – that sometimes the browser isn’t sufficient for your application. Perhaps the user needs to manipulate data while disconnected from the network (on a plane for example or when in a business location without wireless coverage) or integrate with other applications on the device (such as the contacts, tasks or messages application). This session is an new and improved version of a session I did at the View Domino Administrator/Developer Conference in Boston earlier this year. I’m going to be building a rich client in Java (for the BlackBerry platform), Windows Mobile and probably Android. I’d like to do iPhone, but I don’t have a Macintosh and just don’t have the relevant skills right now.

Here's a link to the session abstract:

https://www-950.ibm.com/events/wwe/lotus/lsph2010.nsf/sessionabstract?openform&sessionid=AD114

Anyway, both sessions should be high energy, very interesting sessions. Please plan on attending if you’re at Lotusphere. The sample code for the applications will be posted to this site in January during the conference.

 
Review of Beginning BlackBerry Development by Anthony Rizk PDF Print E-mail
Tuesday, 01 December 2009 20:54
AddThis Social Bookmark Button

On my flights home from the 2009 BlackBerry Developer Conference in San Francisco I had a chance to read Anthony Rizk’s Beginning BlackBerry DevelopmentBeginning BlackBerry Development. I wasn’t one of the lucky folks who received a free copy of the book at the conference – I’d received it in advance of the event and brought it with me to read on the plane home. Anthony did sign it for me at the conference, so that was fun. When I discovered that the book was on its way, I contacted Anthony to find out about his book and see how it compared to mine. It turns out that they’re very complimentary – they both address beginning developers, but cover different parts of the topic.

The book is really good – I enjoyed reading it and learned some things I’ve always wanted to know. First of all, although the title doesn’t say this, the book is a Java book – targeted at BlackBerry developers who want to get started writing Java applications for the BlackBerry platform. It doesn’t cover anything about web development and only covers the platform (BES and MDS) very lightly. You should already be comfortable with Java development; the book doesn’t cover any of the basics, only the BlackBerry specific stuff you’ll need to know to work on the platform. It’s a rather short book, only about 240 pages, so don’t expect it to cover any particular topic in great detail.

Anthony wrote the book in short lessons, each tackling a different part of the whole picture. The book begins with defining a little about the platform, how to obtain and install the development tools (chapter 1) then how to build a simple Hello World application (required for any beginning development book) and test/debug it in the simulator and on an actual device (chapter 2). Next he digs into what makes a BlackBerry Java application and some specific features/requirements of the platform (chapter 3). In all, it’s a great introduction to BlackBerry Java development.

Once you’re beyond the basics, the book starts building a sample application that illustrates how to build an application’s user interface (chapters 4 and 5). What he does is work you through building a login screen for a sample application then extending it to leverage some features of the platform and also how to tweak and tune the UI components Research In Motion provides to make the application look and feel like you want. While much of the chapters cover topics most Java developers will already know, he addresses the BlackBerry-specific stuff you’ll need to understand related to working with the Research In Motion UI Libraries.

The next couple of chapters dig into some both standard and unique capabilities of the BlackBerry platform: Storing data (chapter 6), Network Connections (chapter 7) and location based services (chapter 8). For each of these, the BlackBerry platform supports industry standards/specifications (RMS for data storage, HTTP connections for network access and JSR 179 for location based services) but also has some special enhancements or supports additional options to allow you to create more robust applications. These topics aren’t covered in tremendous detail, but you leave each chapter knowing exactly what you need to know to begin using these capabilities in your BlackBerry Java applications.

Chapter 9 digs into how to package up your application for deployment (through Desktop Manager deployment, BES Push, OTA Pull or through BlackBerry App World).

Anthony has been a BlackBerry Java developer for a long time, so he really knows what he’s doing and it shows in the book. His writing style is very comfortable and he covers each topic not deeply but well. The book is structured in a way to make it easy to digest each topic before moving on to the next, so as long as you know Java, you should be all ready to go after reading it.

The book’s got some typos and errors, but if you’re an experienced developer you won’t have any trouble spotting them and making the necessary adjustments. It’s clear that they rushed the book out to get it released in time for the BlackBerry Developer Conference, so it’s understandable. Anthony told me he’s building a list of these items and will hopefully get them implemented in the next printing.

If you’re a Java developer and want a quick primer to get you started on the BlackBerry Java platform, this book is for you.

If you’ve been a BlackBerry Java developer for some time, the book may have information you don’t already have, but that’s unlikely. If you’re expecting this to be a heavy duty, deep dive into BlackBerry Java development, you’ll be disappointed (but the title should have warned you away anyway). There’s still no reason you shouldn’t purchase a copy and keep it around to lend to those pesky developers who keep asking you simple questions.

 
Another Review PDF Print E-mail
Monday, 30 November 2009 10:48
AddThis Social Bookmark Button
Peter Strange posted a review of BlackBerry Development Fundamentals to the BlackBerry Development Forums. It's great to see that people are 'getting' where the book fits in the market. You can read the review here.
 
First Amazon Review is In... PDF Print E-mail
Sunday, 29 November 2009 21:01
AddThis Social Bookmark Button

Well, the first review of BlackBerry Development Fundamentals has been posted on amazon.com. Unfortunately it's not a very flattering review. Apparently the reader missed the word 'Fundamentals' in the book's title and expected it to be something else than it is. Just in case you're thinking about purchasing the book - please know that it's a book for new BlackBerry developers, not experienced BlackBerry Developers. It contains everything I know to help a new BlackBerry developer get started with BlackBerry development. It's designed to help a developer understand the capabilities of the platform (both from the server and device standpoint), the limitations of the platform and how to build applications for the device. If you're new, I promise you you'll love it and find it very useful. If you're experienced - you don't need my book and any of the other BlackBerry development books that are coming to market.

If you want a real, unbiased review of the book, please read the following reviews. The first was written by an experienced BlackBerry Developer and the second by an experienced BlackBerry guy who wants to be a BlackBerry Developer:

BlackBerry Development Fundamentals Reviewed (www.notesberry.org)

Review: BlackBerry Development Fundamentals Book by John M. Wargo (www.berryreview.com)

If you're interested in hearing me talk more about where the book fits and more, please read Ben Pijor's interview on www.port3101.org:

Interview with Author and BlackBerry Developer John Wargo (www.port3101.org)

If you've read the book and you find it useful, will you please help me out by writing a review on amazon? I really need people to see more than just that one (bad) review. Thanks in advance!

 
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>

Page 8 of 20

My Book

InformIT (Pearson Education)