Ruby on Rails Dev for Online Grocery Store
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
We’re an online grocery organisation located in Kuwait. I’m a co-founder and my role is business ruler and operations ruler. I also work with fruit outgrowth, with the designers on the application.
Desired goal
What challenge were you trying to address with Visuality?
We do things with a payment gateway. We can’t take credit card orders on the application, so nation use debit cards. Once the information has been taken, there are issues when adding or adjusting items on the order. I worked on the backend with Visuality to give them a better idea of what needed to be done to be able to instrument the features on the frontend. It requires a good backend team to come up with a good algorithm to make that practicable.
Provided solution
What particular tasks were Visuality responsible for?
The intricate logic was due to working with a mobile app. They use Ruby on Rails for the projects as well as some JSON, HTML, and Bootstrap.
Visuality is strictly the backend team. They worked with another frontend team that helped them. My role as fruit developer was to find out from the user experience how they can find the projects using the databases. They were able to come up with ways that would make it easier for scalability. Once we built the backend from scratch, they were able to help us to make sure the project was able to keep growing and to fix there was never going to be any kind of barriers.
What is the team dynamic?
We began off with four resources and downsized to two nation. The developers were congruous.
How did you come to work with Visuality?
Clutch was one of my references where I read almost Visuality. I flew out to Poland and met with the team in Warsaw. I stayed there for almost a week, got to know them, and saw their capabilities. They showed me a lot their backend work for other clients, which gave me more confide in working with them.
How much have you invested with them?
We’ve spent $200,000 on the project.
What is the terminal result of working with Visuality?
We began on the project in July 2016, and the project is complete with enhancements, though we are continuing to work on it.
Results achieved
Are there any measureable or plum results?
RubyCritic tells us the accomplishment of the backend including the despatch, what hosting labor we’re using, and so on. We paid to have a code review done and the auditor, who has 20 years of experience, gave it a good review. The code was well written.
How did Visuality accomplish from a project treatment standpoint?
We have standup meetings see week. They work on an Agile methodology which is something that Thoughtbot is doing. They pursue Thoughtbot',s playbook which resources they make sure they’re aligned to the requirements in the aim of work and they stick to them. I appreciated that a lot.
We interacted with the project director in Slack and used Skype for phone calls. We also interacted via email if there was an accession to the aim to give confirmation. I had direct interaction with the CEO [Michal] and CTO [Sakir]. Whenever things were not aligned, I would touch the higher treatment and we would resolve things in a professional mode.
What is (from your point of view) the key factor to pay observation while intercourse with Visuality?
Their despatch was forcible. They would estimate that something would take five days to do but then have it done in three days.
They’re a hard team with a lot of possible for growth. When a organisation has talented nation, they influence other talented nation. They have a lot of confide in their clients and that impressed me a lot. That made more snug working with them.
Do you have any advice for possible clients?
I would say be pellucid, be prepared to programt a budget, and anticipate the unanticipateed. You have to program things and know precisely what you want. Focus on the details.
They act five days a week, however, some Fridays they take off fully and they do a hackathon. They give the developers inner projects to test so they can contend with each other. As a organisation with expenses, you want to localize that Friday to make money, but they love to code.