Profile dating database are ashley benson and caleb dating
Regardless of what you choose, the process for creating the backend would still be the same.We have a “User” object with basic user information such as username, first name, photos, age, two columns for lat and long.I’ve also always been a fan of Rails Composer when starting up a new Rails project.It helps me handle a lot of the boiler plate such as setting up your mailer, adding a user object and enabling it to work with Devise / Omniauth, setting up user roles, etc.We recently launched Color Dating for i OS and Android about a month ago.
This was probably the trickiest part in building the app and took the most amount of time.
Basically, all you need is for the User model to have a “find_matches” method which returns a list of potential matches based upon the user’s preference / location.
In order to handle profile creation from Facebook, we also had to use Sidekiq with Redis so our profile creation jobs can be done on the background.
The reason why it needs to be asynchronous is due to the time it may take to download and upload a photo from Facebook, the entire HTTP request can take 10 seconds which otherwise would clog up your ability to serve other HTTP requests.
As mentioned, we used Sidekiq, but others swear by Resque.
For an MVP, I don’t think it’s really necessary to go too overboard with data persistence on the client side.