Consequence of not creating variation for large screen resolution
Posted on 2014-04-20
This one's highly subjective.
I'm converting a functioning prototype application into ASP.NET MVC. It features a complex graphic and a complex custom "list" (stack of divs with formatted text, not table, or li). It's used for collaborative process design. It's currently got 100K+ lines of C# and maybe 25K of JS.
It's the kind of thing that's likely to shared via Webex or similar utilities.
The JS and CSS currently all use fixed pixel dimensions, based on the assumption of a 1024x768 screen resolution...except that many of the element dimensions are dynamically created in JS anyway.
The business model doesn't require a mobile version, for now, so I don't have to worry about smaller resolutions.
My concern is that the target audience does include IT project managers and business analysts, along with other knowledge workers. And I'm seeing more and more of them use higher resolution monitors (like 1600X1200 or more).
The graphic has a slider that can increase or decrease the size of the graphic and graphic labels from 50% to 200%. Needs some fine tuning but mostly works ok.
I'm thinking I can build a similar slider to adjust the div and font sizes of the "list".
But the whole thing is still currently locked into this 1024x768 based-layout of fixed divs. I suppose I could make that adjustable too.
I see and generally understand the many techniques available for detecting screen pixel dimensions, using % for dimensions, using alternate css for different screen sizes etc.
Having said all that, the question has three parts:
1) Any thoughts about how many business and IT staff (not hard core engineers, particularly) are using their monitors at 1280X960 or more?
2) Any thoughts on how much negativity would be engendered by not having the app adapted to higher resolution screens?
3) Any thoughts on the relative effort of going ahead to make the app responsive to higher resolutions, given the total amount of code it contains now, the large portion of current code-based size setting, and the built in scaling functions? (And I could convert first, allow for the sizing, and refine the sizing later)
As I said, highly subjective.