Great little session on the look and feel and where we are headed. See attached. Also, here is a small copy of the verbage for the summary we did today.

-- from the attached file under a question about the look and feel and user interface.

Summary: When we started Adilas we decided that we wanted to get functionality done first, followed by look and feel. We know it is time to bring that pretty, modern look and feel into play. Some of these aspects are already being approached and more are on the horizon. 

We have chosen to let the clients lead with their ideas, suggestions, priorities, and funding. This has directed our development and our growth thus far. We recognize that many people would like us to just spend the money and make everything pretty, but then you still may not make the goal or hit the mark, which is continually changing. We feel it is important to keep following the client's lead and this will still be our main approach. 

Having said that, we are definitely planning on extending more services, continuing to evolve and refine the interface, and keep following what is working. This will include getting a master plan in place. Many people have heard us talk about this concept called "fracture" - which is a name for a future project which will be a configurable, dynamic interface that will only turn on whatever pieces you want to see. Fracture will include countless ideas, lessons learned thus far, ways to improve efficiency, and breaking things into smaller modules and pieces. This will include more efficient navigation, dashboards, and user friendly features. 

It's beyond the scope of this summary to fully explain here but this will be incredibly powerful to be able to configure Adilas to whatever level of complexity or simplicity you want. This is like an iceberg mountain analogy. You still have the whole mountain but you only expose what you want to see - just the iceberg portion on top. It can make it feel easier, simpler, and more manageable. 

The current model is composed of numerous, smaller prototypes that have been linked and wired together. Our eventual goal with fracture is to make all of those prototypes have the same look, feel, and flavor. This will be selecting the best of class from over the years and standardizing it across the platform/system.

Even though we are talking about look and feel, taking a team approach, helps us move forward in every aspect of furthering the application and model. People who work together are able to achieve more and that is how we are trending and changing our operations even further. More good stuff to come.

If you type the word "fracture" into the developer's notebook you will begin to see how big our plans and dreams are for what we want to accomplish when we build to this "fracture" plan.