Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Hoping someone can help me out. If I’m developing a Rails 3 app, but later would like have a mobile version later down the line, whether is iphone/bberry or anything else. Does this mean that the mobile apps will be developed from scratch or will they utilize the existing infrastructure somehow?
Does anyone have experience with this?
Thank you!
It depends on what type of mobile app you’re talking about. You can create either:
If you go with #1 all you need to do is create phone friendly versions of your views. But your users will need to use the web browser on their phone to view your site. An example of this is http://www.engadget.com versus m.engadget.com. The latter is just the engadget website optimized for viewing on your phone.
If you go with #2, at the very least you’ll need to create a native client app on the platform you select. However, if you design things right you can leverage much of the functionality that’s already in your website.
Take twitter as an example. You can use the twitter website to use features of twitter or you can use a native iphone app like twitterific. The iphone app (probably) uses some twitter API to access functionality that’s the same as when you use their website.