1 / 49

Rob Wenger CEO / Chief Technology Officer Higher Logic

The Next Big Thing in User Experience Development: UI Controls PRESENTED BY: ROB WENGER, CEO/CTO, Higher Logic. Rob Wenger CEO / Chief Technology Officer Higher Logic Social Networking, Community, Collaboration Previously Principal Architect at ASI ( iMIS )

brac
Download Presentation

Rob Wenger CEO / Chief Technology Officer Higher Logic

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Next Big Thing in User Experience Development: UI Controls PRESENTED BY:ROB WENGER, CEO/CTO, Higher Logic

  2. Rob Wenger CEO / Chief Technology Officer Higher Logic Social Networking, Community, Collaboration Previously Principal Architect at ASI (iMIS) CTO of Active Matter – Web Design & Web Products Who Am I?

  3. Explanation of Control Based Development Demonstration of the advantages Design a Landing Page Using Parameters to Configure .NET/SharePoint Web Parts Use in Cross System Integration Fun projects (that are useful!) Summary and Q&A Agenda

  4. How many of you are: Developers IT Managers IT Other Non-techies Quick Poll

  5. What platform does your org use? Microsoft (.NET, ASP, VB, etc.) Open Source (PHP, Ruby on Rails, Python, etc.) Java Cold Fusion Other Quick Poll 2

  6. Web application developers are used to “Pages” In this model, Think Smaller Think in terms of functional blocks Build pages from blocks Reconfigure blocks for new or different audiences Add or remove blocks for new functionality Choose a framework that makes the above easy Component Based Development

  7. New pages, Same Parts Full View

  8. New pages, Same Parts Summary View

  9. New pages, Same Parts Summary View

  10. New pages, Same Parts Summary View

  11. New pages, Same Parts Summary Listing

  12. New pages, Same Parts List View

  13. New pages, Same Parts List View

  14. New pages, Same Parts List style

  15. Reuse Easy “customization” for different uses or audiences Small projects get finished! Small additions can have a big effect Advantages of Component Based Dev

  16. A page at which visitors (users) arrive on your site (application) after clicking a link Home page Section home page Personalized home page Typically designed to get the user to do something. Landing Page

  17. Our Goals – Get Visitors to: Complete their profile Engage in discussions Donate Connect with their peers Respond to the Call to Action of the week/month Let’s design a Community Landing Page

  18. If not logged-in, say Login If logged-in but no profile, say Enhance your Profile If profile is started but no (or few) friends, say Connect with Colleagues If has more than 4 friends but no communities say Join Communities If in communities do Call to Action ButtonText parameter ButtonLink parameter E.g., Donate, Renew, Write your congressman, Register for the conference Action Button Control

  19. Each control must be able to exist on its own Input is via parameters or URL parameters Flexibility thru configuration, via parameters Output is simple HTML that can easily be styled. Use semantic tagging. Always keep reuse in mind HL’s Rules of Control Development

  20. Parameters (AKA Properties ) are component level settings, used for: Input of data or “keys” Control of what is displayed (Show/Hide) Setting use specific configuration Title Text Links Format Etc. Input and Configuration via Parameters

  21. Non-visual components can affect page behavior, just by their presence Check security Add logic Get shared data Perform tasks Components Don’t Have To Be Visible

  22. Built into .NET Key function in SharePoint (MOSS) Allow for changes at run-time (My MSN style) Allow for connections between parts to share data Easy to use UI for Add, Move, Delete, Configure Well known interface allows 3rd party web parts Web Parts

  23. A page is made up of Zones Each zone can hold multiple parts Zones might come from a template or layout Web Part Zones

  24. Anatomy of a Web Part Title bar Zone Name Add Button Title Menu Content

  25. SharePoint Web Parts Configuration Menu

  26. Web Parts Properties Pane • Change the properties, appearance, layout • Shared – change for everyone • Personal – changed by/for an individual user

  27. Web Parts Connections • Connect Web Parts on the same page together • Exchange data between them • Set parameters/properties of one from another

  28. Web Parts Connections

  29. Controls for Seamless UI Integration • Web services for grabbing 3rd party data • Controls to display web service data • Intermix with local controls, other 3rd parties, on one page

  30. Example of Cross-System UI Integration • Local content from the CMS • Recent blogs from the Community site • Upcoming events from the Registration system • Thermometer from Fund-raising system • Renewal notice from the Membership system • Photo slideshow from Flickr

  31. Once you start thinking small, you can make a big impact with very little (relative) effort.

  32. Vista Sidebar Gadget • Management can watch without running full system • Calls to backend using web service • Properties set with configuration screen • Near real-time data

  33. Mobile App • Road-warriors lookup customers from mobile • Very simple web app • Login • Menu • Form • Result

  34. Summary • Think Small! • Build bricks, then assemble them • Reconfigure for new uses • Blur the lines between disparate system • If possible, choose a framework and toolset that makes this easy • Think outside the box

  35. Q & A

More Related