XPages and Me

My Journey into XPages Development

Dabbling in Bootstrap and Font Awesome Part 7: All these shiny new toys! What now?

When I first started dabbling in Bootstrap and Font Awesome, I was very excited and loved the look and feel of the framework. When I say dabbling, I mean that at the beginning, I didn’t really think about, how I am actually going to use it. I was just playing around with, getting a feel for how it all works and how I can integrate it with XPages.

But eventually I was faced with the question: What am I going to do with this shiny, new framework; How do I apply it to my daily development work?

I realized, I’ll have to rethink the way I develop my applications. Not necessarily the coding itself, but how do I set up the front-end, the UI, the part that the user will eventually see and will have to deal with on a daily bases.

I was always determined to design the UI of my applications in a way, that would aide the users in completing their daily work, even in the Notes Client (I guess it can be considered a job well done, if a user asks you, if your application is a web application, even though it is plain Notes Client). I was a big fan of Chris Blatnick’s blog Interface Matters and a lot of my UI designs had been inspired by his posts.

I think what I am trying to say is, we as XPages developers need and should also always think about the UI, to make it easy for the users to do their job.

If you don’t know how or what to do, talk to your users; sit down with them and observe them doing their daily work and it might give you ideas as to how to make it even better and easier for them.

The code in the background can be as sophisticated as can be, if the UI makes it hard for users to use an application, they will hate it and those users won’t make good advocates for Domino and XPages.

What is your opinion on this matter?


2 responses to “Dabbling in Bootstrap and Font Awesome Part 7: All these shiny new toys! What now?

  1. Patrick Kwinten October 4, 2014 at 7:38 pm

    I would first determine if usability is a requirement. if not: arrange funding / resources / time for it. it should be clear in the project definition that there is time reserved for usability application.

    • Daniel Friedrich October 6, 2014 at 11:26 pm

      A quick way to make things easier for a user, especially in a workflow application, is to initially display only what is relevant to the current user’s role, with an option to see more if the user so wishes

      For example: The approver sees only requests that require his approval, or the requester sees only requests that have been returned to him / declined.

      If the UI design requires a lot of work, I do agree with you.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: