On mobile applications time response is one of the key aspects of this ecosystem.

Some of the key points that influence on time response are:

1.- the type of application: native application or modified application from another application layer.

2.- The telecommunication channel used for the device (3G, 4G or Wifi connection).

3.- Testing of the solution: this is key for the solution, you not only need to test the functionality, you need to test Google web services, and other third party services to understand bottlenecks), test # of redundant users, etc… so many of the

4.- Architecture / platform decision, this will represent the main issue and one of the key decisions for the rest of the project. People working on robust business cases and a clear medium term road map do not use to fail on this point, but for the others the situation can be different.

If you are going to build a solution for mobile devices you will have to make so many questions about the type of user, #redundant people, peaks of use, look & feel. Sometimes the functional part is the easy part.

I had an issue with the trackpad of the BB that I would like to remind (link).

I had the BB in the pocket and probably some keys + the trackpad was pressed in a sequence that I still do not know.

The issue was that the vertical move of the screen was stopped in some screens: an e-mail, main screen… and I was required to press the “alt” key to move on the screen. There were no physical issue, for instance on the e-mail inbox the move worked perfectly.

What I did to recover the initial configuration was to install an application and uninstall it. The complete reboot made the issue disappear.

Unfortunately for me I still do not know the sequence of keys I have to press to have the issue resolved.

Planning the test plan on the mobile application, some of the questions we have asked are:

How can I see an error on the mobile device?

How can I measure the response time for each mobile action?

Which actions do I need to check in order that the service support has visibility on the mobile errors?

With it, some of the answers are:

The blackberry simulator has a lot of configuration options that allows you to simulate: Status of the battery, Quality of the signal… it will allow us to measure the response time in different conditions.

There is the possibility of adding logs on the mobile side using Javascript: Logger.log(“Before Request event1″,””,Logger.WARNING);

We need to publish a method in the WSDL that allows us to log the mobile errors in a common database. The service support needs to know which errors are happening, the log of the mobile device seems to not be accessible by the service support in a centralized container.

We need to define it very well because this phase is going to be hard.

We are studying how to deploy lotus applications with MDS Studio & WSDL.

The starting was easy, but the real problem has started when we have tested the security of the Blackberry device to the Lotus Notes database.

We have been investigating about the Lotus Notes sessions creation and there is no easy way to get the session accesing with the the WSDL. I have done applications accesing using DIIOP and the NotesFactory object but this approach does not convince me at all.

Now we are thinking about to get the session using the POST method on the “?login” page of the Domino server and trying to use that session for the mobile user.

The questions that round my mind are:

– Is going to be possible to get the session with this method?– Is able the Blackberry to store that session for next calls to the Lotus Domino Server?– How is it possible that I have not found nothing about this problem on the Internet?