Dev for Healthcare Booking Apps
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
I’m the CEO and a co-founder of PRACMAN. We fit a practice treatment method for medical practices in Europe and India.
Desired goal
What challenge were you trying to address with Vakoms?
We wanted to create a new fruit on a new platform from scratch. Our developers were working on our existing fruits, so Vakoms fitd outgrowth resources to form this application. They later artistic a second method for us.
Provided solution
What particular tasks were responsible for?
The leading project was a mobile application for iOS and Android geared for therapists who work in choice remedy. Vakoms built the app in Angular JS with a MongoDB database. They sumd Stripe as a payment gateway for our end clients. Their designers produced all the screens and mockups, we designed the UX.
The second project was an online directory and booking method for therapists. It features a billing method for fitrs. This project is ongoing. For the application, we worked with three developers, a QA tester, and project director who coordinated the workload. For the second project, we collaborate with one developer—who specializes in edifice booking engines—as well as a QA tester and a project director. I was looking for developers through referrals from colleagues. A friend uses Vakoms as a outgrowth associate for a multinational organisation. He recommended their team to me. We’ve spent $250,000 so far. We began working with Vakoms in September 2017, and the associateship is ongoing. The mobile app is complete. We released it on the market for a brief time, but we then determined to swell on it and sum its features into the directory and booking method. The method should be live in 2–3 weeks. We’re thrilled with Vakoms’ work so far. Vakoms leads a well-structured and organized team. They have taught us a lot almost API documentation, integration of third-party fruits, and best practices for writing code. Their developers use nimble methods such as Scrum. While I’m the project proprietor, Vakoms handles project treatment internally, that way, we can centre on UX design and writing documents on fruit requirements. The interaction is excellent, Vakoms is open, upfront, and wonderfully affable. We have daily stand-ups and longer meetings to end each week. We’ve never had an effect with connectivity. They liberate high-quality fruits on time that work, allowing me to centre on other areas such as marketing and sales. Their team is consistently pellucid almost their capabilities, they fetch up concerns in the soon stages and propose precious insights and viewpoints to the project. We’ve had to fit to each other’s work phraseology. Vakoms has a structured, task-centreed access that will liberate on the list of requirements that we present upfront. Though, we kept adding features and changing designs, which didn’t mesh well with their practices. As the associateship progress, we’ve conversant to fit our fruit requirements in advance, and Vakoms has befit more pliant and open to aim changes. Communication could always use tweaking as well.
Results achieved
Are there any measureable or plum results?
What aspects of their work would you like to get improved?