You will almost always find that as your mobile app and web app grow you will require changes to the API. This is why a versioned API enable you to not worry about crippling old mobile clients and move new clients onto the new versioned endpoints.
It may be temping to just to "re-use" the existing Rails controllers -- and may in fact be the way to go if your app is small -- but in a large app this gets very messy very quickly. Also if you are "re-using" the existing Rails controller because those controllers contain domain logic, then you should refactor your domain logic out of the controllers and into domain objects. Building more controllers actually encourages you to do this, which in the end creates a cleaner architecture (although I would caveat that it may be more work up-front). -Jason On Aug 25, 2014, at 10:42 AM, André Orvalho <[email protected]> wrote: > Well It's more like a question for the future. If I need a app to start > with, is it a good practice to still do the website and use the common API or > to just develop the app? > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/243FE511-A59A-4F44-8958-A70A8E10E3D9%40datatravels.com. For more options, visit https://groups.google.com/d/optout.
