I've done it by adding specific layout, templates and stylesheet to the existing app.
You can trigger events in your project configuration upon user agent to change templates and specific configuration. The strategy to use another app depends wether your mobile app should have the same functionnality as the 'classic' web app does, but it will be easier if most code still shared. -----Original Message----- From: Kevin <kevinb...@gmail.com> Sent: mercredi 1 septembre 2010 12:51 To: symfony users <symfony-users@googlegroups.com> Subject: [symfony-users] mobile site strategy I am wondering what others have done to create a mobile site for their symfony projects (when more than just a handheld stylesheet is required). What I am planning on doing is moving all my modules to a plugin and creating another app called 'mobile'. I can then override any modules I need optimized for a mobile device. What strategies have you come up with? Is there an agreed upon best practice? -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
