Dating style template men with children dating

Especially in the earlier stages when your backend’s schema is more volatile and you’ll probably end up wasting a lot of time having to do a lot of pesky migrations.

The only thing you would need client side persistent storage for is your “User” object.

I’ve also always been a fan of Rails Composer when starting up a new Rails project.

We originally tried integrating various pre-built chat solutions but they all back fired.

It ended up taking way longer to customize the libraries than we had thought and by the end of it, we had a half working solution that was very poorly written and hard to maintain.

Luckily, if you’re on Rails, it comes already packaged with a JSON serializer and if you’re using Alamo Fire (which is my preferred HTTP library for Swift), it also comes equipped with a JSON to Swift object deserializer as well.

If you’re on Objective-C, the ASIHTTP library also handles JSON serialization for you.

But even if you’re not making a card view / swipe type of app, the same principle applies: Don’t reinvent the wheel.

Go on Github, do a search and see if there’s already a library that can help you with what you want to achieve. I know there are a lot of other web alternatives out there, and people have varying opinions, but for me, Rails has always been the fastest and most straight forward way to quickly deploy a CRUD (basic) backend server.Alternatively, if you were more used to interpreted languages like Java Script, Ruby or Python, then Swift may be more up your alley.When programming, so much time is wasted rewriting the same functionality that has existed before.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.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.

Tags: , ,