6. Trends RichComprehensive interaction with the user InternetRuns in a web browser / smart device ApplicationSoftware with purpose: solve one or more tasks! (no website!) + Cloud Computing The combination of RIA and Cloud Computingcould be the future of software!
7. Trends 12.01.2011 Folie 7 "Rich Internet applications (RIAs) are emerging as vehicles to enable the next generation of Information Workplaces that are best suited for decision-makers and task-oriented workers who engage in complex, multistep processes — people who need seamless, individualized, and highly visual user experiences." Forrester Research
8. Trends “In the cloud” Gartner: cloud computing will be as influential as eBusiness Widely accepted classification and definition of “cloud computing” was made my Berkely Above the Clouds: A Berkeley View of Cloud Computing: http://www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-28.html Infrastructure as a Service (IaaS) Platform as a Service (PaaS) Software as a Service (SaaS) Johannes opinion: cloud == just a fancy word for a very big computer network 12.01.2011 Folie 8
9. Trends 12.01.2011 Folie 9 “In the cloud” IaaS Amazon, GoGrid, Rackspace, Terremark, Windows Azure PaaS Google AppEngine, Heroku, Bungee Connect, Force.com,Windows Azure (combination of IaaS and PaaS) SaaS Salesforce.com, Google Apps, Zoho, SAP Business byDesign* Application service provider (ASP) is a business that provides computer-based software services over a network. (more than just hosting!) * Is not running in a real cloud, multi-tenanthere!
11. Trends 12.01.2011 Folie 11 Source: http://www.keithpij.com/Portals/0/Downloads/IaaS,%20PaaS,%20and%20the%20Windows%20Azure%20Platform.pdf Keith Pijanowski, PlatformStrategyAdvisor, Microsoft
12. Trends 12.01.2011 Folie 12 Source: http://www.keithpij.com/Portals/0/Downloads/IaaS,%20PaaS,%20and%20the%20Windows%20Azure%20Platform.pdf Keith Pijanowski, PlatformStrategyAdvisor, Microsoft
13. Trends 12.01.2011 Folie 13 “In the cloud” Pros: less costs (through virtualization), easy deployment, scalability, system maintenance, reliability, self-service, on-demand, pay-per-use time to market! Cons: not every SW can be virtualized, proprietary software everywhere, restrictions, short lifetime of nodes, unsatisfying application management, impossible change of cloud service provider, security concerns, third parties reliability outsourcing of important knowledge / core business!
15. 02 12.01.2011 Folie 15 RIA Patterns Source: Presentation from Bill Scott (Yahoo! Ajax Evangelist) “RIA Patterns - Best Practices for Common Patterns of Rich Interaction”
16. RIA patterns 12.01.2011 Folie 16 RIA patterns as framework elements invitation. cursor invitation. hover invitation. tooltip invitation. page invitation. drop invitation. available. selected. auto complete. live suggest. refining search. dynamic filtering. live search. on-demand scrolling. deferred content loading. fresh content. on-demand content. periodic refresh. resizable modules. scrolling modules. hover detail. narrowing actions. narrowing choices. auto form fill. in-place drill down. dependent choices. look before you leap. drag and drop. drag and drop modules. drag and drop objects. persistant portals. in page edit. inline text edit. inline custom edit. direct state edit. rating an object. inline custom edit.
18. RIA patterns 12.01.2011 Folie 18 “What’s changed with Ajax is: You can have a pipeline of just-in-time information delivery. How you manage the flow of information into a page is very important to keeping the user in the flow.” Bill Scott, 2007
19. Trends Anatomy of an RIA Pattern Interactionevent, timer, invitation Operationlookup, action, validate, message Presentationupdate to the interface 12.01.2011 Folie 19
20. Trends Interaction Every pattern starts with an interaction Event: User event Timer: System event Invitation: Inviting user interaction (teasing) 12.01.2011 Folie 20
21. Trends Operation Every pattern causes on or more operations User centered design requires: Lookup. I can get information when I need it. Action. I can take action in context. Validate. I can prevent errors early. Message. I can communicate instantly 12.01.2011 Folie 21
22. Trends Presentation The interface changes in a meaningful way Challenge: Avoiding confusion Indicators should be less fancy and more “natural” (the art of simplicity) e.g. busy indicator. progress indicator. inline status. opacity fade. 12.01.2011 Folie 22