E-commerce Trends Popular in 2019

The prospect of growth in the e-commerce industry has just begun to reform the way people trade. The exponential expansion observed during the last 10 years in the online retail sector does not approach a saturation point but marks a sunrise of brand new innovations which would further transform the means of conducting business online.

Read more


Vinsol is a Choice for Transforming The Software of Your Company!

At Vinsol, we consider ourselves pioneers instead of simple coders. This sets us apart from our competitors because it drives how we approach problem solving. With an extensive team of talented Ruby on Rails, iOS and Android developers, Vinsol can provide solutions that range from a few dedicated iOS resources to complete, end-to-end project implementations. We understand that every client is different and so, too, are their needs. This awareness in combination with our methodical approach has allowed us to satisfy clients in North America, Europe, Australia, Africa and Asia for over well over a decade.

We are delighted to announce that for the second year in a row Clutch has recognized us as one of the top developers in India. This year the report 2015 Top Web Developers India, showcases a series of outstanding developers with proven track records of client success. Read more


User Phone Verification - A way to prevent fraud in e-commerce

Recently in one of our e-commerce projects we implemented phone verification for users to have authentic accounts at our website. The requirement was to have one account per user to avoid misuse of offers provided by our service on scenarios like signup, high-value purchase, referring a new user to shop at our site plus other special offers.

So we decided to verify users using phone number verification that seemed more reliable than email verification since having multiple phone numbers is not as easy and rare as compared to having multiple email accounts. We then chalked out a simple approach that came out ineffective and needed a renovation.

Initial Approach:

Save a phone number corresponding to a user that he can verify later by the one time verification code sent to his phone. We then ensure that the phone number is not verified against other account to have an account per user on verification request. Things seemed to go well but didn’t serve the purpose as expected.

During our revisit to the approach we found out that a user still could create multiple accounts. If you missed it too, here is how it goes:

Suppose, a user say, Haitham signs up with account A1 and verifies his account with number, N1. Now once he needs another account to avail more offers he can simply edit his number to say, N2 and not verify it. Then he can create another account say A2, and verify this new account using N1. As in the application’s use case of 'referring a new user to shop at our site', he could add himself as a referrer using account A1 for A2. Hence, the whole idea of fraud detection and prevention was deceived.

Magic Trick:

Don’t associate a number with a user until the user verifies the number.

The simple change above solved our issue to all possible levels.
Read more


SSL checklist for Ruby on Rails Applications


The purpose of SSL is to provide a reasonable level of protection against eavesdropping and man-in-the-middle attacks. Although SSL provides a greater level of security, it introduces a lot of overheads and hence should be used sparingly. Two of the most common places to use SSL is for payment transactions and user registration/login.
This post intentionally focuses only on the Rails application as there are numerous post on the net for SSL setup on the server. Enabling SSL in a Rails application is really trivial and there are just a few points that need your attention..
Read more


Git Work Flow For Ruby on Rails Developers

This is my very first blog post and so I thought it should be about a tool that is indispensable for me - Git. I started using git about 10 months ago and looking back I can't imagine how I managed to get work done without it. The purpose of this post, however, is not to sing git's praises, there are lots of good articles on the web that do so much better than I ever could. Instead, I wish to share the work-flow I use on my projects. I developed this work-flow by trial and error over the months and is currently the most efficient and productive approach I can think of. If any experienced git users happen to stumble upon this post, please do provide suggestions/alternatives to help me improve my process.

The project I am currently working on requires me to maintain two parallel deployment branches. One is a "production branch" which is deployed on the live server and the other is a "development branch" which is deployed on a staging server. All enhancements and feature additions are done in the "development branch" and the only changes made in the "production branch" are production bug fixes that need urgent attention. Once the "development branch" is deemed stable it is merged into "production branch" and deployed.
Read more