User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have some problems trying to design layout and navigation structure for BlackBerry app. The basic of our layout is consists of two headers that will be fixed so that when users scroll horizontally or vertically these two headers will be fixed.

Upon developing and research, scrolling div (using overflow) and fixed headers are not recommended for non-touch screen devices or devices that uses trackpad/trackball.

And then another problem I discovered is that on touch-screen devices, even though the scroll container has overflow:auto, but there are no scrolling bars on app when tested on the device. (I have tried testing it on 9800(OS6.0) and 9900(OS7.0).

Is there any good solution or workaround to this problem?

share|improve this question

closed as off topic by Erics, Benny Skogberg, JohnGB, JonW Dec 27 '12 at 12:36

Questions on User Experience Stack Exchange are expected to relate to user experience within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

Is this an HTML5 app? Web app? If so, be prepared for some huge headaches if you are supporting OS6. The blackberry web browser/OS is extremely buggy. I call it the "IE" of mobile phones. – DA01 Dec 3 '12 at 16:14
Yupz. Is is developed on WebWorks using HTML5, CSS, jQuery. – Jamie Dec 4 '12 at 0:53
I haven't done anything with OS7, but OS5 and 6 had serious issues. OS5, for sure, had all sorts of issues if you tried to update the DOM. OS6 was better, but we still had to write a lot of work-arounds just for blackberry. And I don't think I'd call OS6 HTML5 compliant by any stretch. The best advice I'd have is to just keep it as simple as you can if you're targetting BlackBerry. – DA01 Dec 4 '12 at 1:03
Maybe you need to be a bit more specific on what is the usability issue here so that you get (better) answers. Try editing your question and point out what exactly is the problem. If your problem seems to be more of a technical nature then you might want to try ask over at and close this question here. – kontur Dec 17 '12 at 10:08