We provided an internal session where it's was promoted a internal discussion about the comming trends of ui interfaces like backoffices. Architecture, UI guidelines, best pratices, and so on.

1. Developing Backoffices
A brainstorming session
10.Nov.2011
Rui Estevão
Gonçalo Chaves
Viatecla

3. The world did change
Know your audience | LISTEN
Users don’t expect to see postbacks
Users typically don’t tolerate slow pages
Users expect to use systems that represent current time
tendencies
Traditional is the least for expectation
Users want to be surprised (positively )
All this is true for unpaid content… but…

4. The world did change
Our products have “expensive”*
licensing
Each screen that is not good kill’s our business
The main question we have to ask when we complete a task is:
“Would I pay for it?”
* They are not expensive for their added value, however the number is big… and
everything is about numbers

5. The world did change
We should be ready to sell as a service
To do so, we should think as a service
ISOLATE, REUSE, SHARE
Identify oportunities | Sell online |
charge less, charge more often

6. Main “things” to consider
more important than tecnology
• Cenario / Context
• User Interface
design
look & feel
• User Experience
Performance
Number of clicks
Feedback

7. Backoffice’s mission
Not only
Help “Operators” to do their job
But also
Help Developers in development
Code Snippets
Ready to use User Controls
Query Interfaces | Data Extraction
Out-of-the-box Services

8. Backoffice’s mission
Every developer is an Architech?
Should ask, should share
Back to services models
SOA, REST, XML,JSON…. U name it :P

9. Backoffice’s mission
See the good samples – fb, ios, wp7
Cross user experience between interfaces
Focus development, RAD app? MS mytho
Know the system, learn with the system
logy

10. Backoffice’s mission
Ok… so:
How are we doing it?
How should we be doing it?
How will we do it?

11. Estrada da Algazarra, 72
2810-013 Almada
Portugal
T. +351 212 723 500
F. +351 212 723 509
www.viatecla.com