• Save
RichFaces 4 rolling to Mobile Era
Upcoming SlideShare
Loading in...5
×
 

RichFaces 4 rolling to Mobile Era

on

  • 2,295 views

RichFaces 4 rolling to Mobile Era ...

RichFaces 4 rolling to Mobile Era
A session at JSF and RichFaces Workshop/Conference

Mobile devices and smart phones are rapidly becoming the primary web client for significant amount of users. For the web developers it represents new area where they should focus when developing applications. They need to handle device specifics as feature support and display possibilities.

RichFaces is opening doors for engineers which are focused on application development and rely on framework to handle consequences. RichFaces comprises suite of component which is optimized for use on both, mobile and desktop clients.

Lukas discuss where HTML5 and CSS3 fits into the picture and how can JSF and RichFaces

Statistics

Views

Total Views
2,295
Views on SlideShare
2,295
Embed Views
0

Actions

Likes
1
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

RichFaces 4 rolling to Mobile Era RichFaces 4 rolling to Mobile Era Presentation Transcript

  • JSF & RichFaces Conference UNIQA RichFaces 4 Rolling into Mobile Era by Lukáš Fryč 9.9.2011
  • Introduction
    • Lukáš Fryč
      • [Luka:ʃ Frɪdʒ]
      • @lfryc, #RichFaces
    • Software Engineer at JBoss by Red Hat
      • RichFaces Core Developer
      • Seam, Arquillian and HTML5 enthusiast
      • JBoss Testing Initiative member
  • Agenda
    • Mobile Development
      • Considerations & Requirements
    • JSF / RichFaces on Mobiles
      • Current standing
      • Future goals
  • Checklist
    • Are you familiar with...
      • today's mobile requirements?
      • JSF support of mobile devices?
      • insight what is currently baking in our labs?
  • Are You a Mobile Developer?
  • Mobile Developer?
    • Do you have mobile requirements?
    • How about the near future?
  • Mobile Developer?
    • Even if you said NO
    • The answer is probably YES
  • Why YES to Mobiles?
    • 1 billion smart phones today
    • 2014: mobile internet > desktop internet
    • 2011: 53% of companies will have deployed iPhones
    • 2015: Tablet revenue to surpass $49B
    • ...
  • Are you prepared?
  • Are you prepared?
    • Does your boss know what he wants?
  • What do you need for Mobile Web?
  • What is mobile web?
    • Mobile web application is like any other
      • With escalated demands
  • Things to Consider
    • Context and Navigation
    • Design & Usability
    • Resource Loading Optimizations
    • Device and Feature Detection
    • Technology Details Experiences
  • Context & Navigation
    • Why is the user accessing your site?
      • From what?
      • From where?
      • Why?
    • Limit transitions and clicks
  • Design & Usability
    • View port & Scaling
      • Limit scaling
    • Don't rely on resolution too heavily
    • Avoid internal scrollbars
    • Keep touch interface in mind
  • Design & Usability
    • Load only data that are needed
    • Avoid fluff & complex branding
    • Don't launch new pages
  • Device & Feature Detection
    • Header Inspection
      • Operating system
      • Browser type & version
      • Can infer
        • Carrier
        • Country
        • Device brand & model
  • Summary
    • Mobile web application is like any other
      • Additional demands
        • Technology Knowledge
      • Elevated demands
        • Developer Experience
        • Compatibility Testing
  • Where does your framework fit?
  • Where does the JSF help?
    • Facelets VDL
      • Powerful view definition and templating engine
    • Render Kits
      • Desktop, mobile
    • Cross-cutting concerns
      • JSF delegates to custom implementation where specification falls short
  • Cross-Cutting Concerns
    • Resource Loading
    • Partial State Saving
    • Behaviors
  • Is it enough?
  • Is it enough?
    • YES it is
  • TweetStream app
    • RichFaces Push
    • HTML 5
    • CSS 3
    • Feature detection
      • Server-side device detection
      • Client-side feature detection
      • Client-side layout and orientation detection
  • Is it really enough?
  • It is really enough?
    • NO it isn't
      • Leads into home-spun solutions
      • Frameworks to fill the gap
  • How can RichFaces help you?
  • Filling the gaps in JSF
    • Push data
    • Resource loading
    • Device & feature detection
    • Layout & orientation support
    • Navigation enhancements
    • Mobile-ready Components
  • Push Data
    • Updates page content
    • Immediately
    • Integrates with Atmosphere
      • Comet/Websockets
  • Push Data
    • JMS
    • TopicsContext
    • Direct DOM update
    • Partial Page Rendering
  • Resource Loading
    • Optimal way
      • Download only required resources
      • Minified
      • Compressed
      • In single file per resource type
        • HTML, CSS, JavaScript
    • Initialize JavaScript when page is ready
  • Device Detection
    • Provides device-specific metadata on the server
      • In simple way
      • Which you can use for customizations
      • Future proof
  • Feature Detection
    • Provides client-side metadata of detected features
      • CSS classes
      • JavaScript API
  • Layout and Orientation
    • Layout Templates
      • Desktop
      • Tablet
      • Smartphones
    • Including support for orientation changes
  • Navigation Enhancements
    • Providing user with progress
      • Status indication
    • Bookmarks support
      • Supports AJAX
  • Navigation Optimization
    • Pre-loading
      • Content
      • Resources
    • Smooth transitions
      • Near native experience
  • Two Paths
  • Mobile-ready Components
    • Two paths
      • 1) Supporting mobiles
        • Current application
      • 2) Targeting mobiles
        • Components targeting specific requirements of mobile devices
  • 1) Support Mobiles
    • Don't mess with mobile-specifics
    • Trust the framework
    • Don't lose usability
  • 1) Support Mobiles
    • Desktop application on mobiles
      • View-port is not optimized
      • Clients needs to scale
    • Optimized page layout
  • 1) Support Mobiles
    • Mobile integration today (4.0)
    • Testing for device compatibility
    • Full-support in 4.1 (Fall 2011)
      • optimized RichFaces Showcase
    • Enterprise support available
  • 2) Targeting Mobiles
    • Targeting mobile-specific needs with
      • User Experience
      • Navigation
      • Optimizations
  • Mobile Showcase
  • Wrap up
  • Conclusion
    • JSF doesn't target mobiles
    • Extension libraries to fill the gap
      • Develop in component-oriented way
      • Care about good-practices
      • Leave the hard-job to library
      • Reuse what you already know
  • Checklist
    • Are you familiar with...
      • today's mobile requirements?
      • JSF support of mobile devices?
      • insight what is currently baking in our labs?
  • Feedback
    • RichFaces Community Forums
        • bit.ly/9hRNzd
    • irc.freenode.net #richfaces
  • Follow Up
    • [email_address]
    • Twitter: @lfryc #RichFaces
    • rik-ansikter.blogspot.com
        • bit.ly/oKlSKF
    • Planet RichFaces
        • All RichFaces bloggers
        • bit.ly/r1CSob
  • RichFaces 4 Rolling into Mobile Era Q/A by Lukáš Fryč