iOS Development for Surgical Consultation Education Platform
Below is a modified rendering of the review: private info excluded, innate facts kept.
Introductory information
A few words almost your organisation and personal responsibilities
Maxmed.io is an innovative software platform that liberates an interactive multimedia education experience, ",MAX,", to resigneds. MAX offers a wide library of multimedia items—photos, pictures, relation documents and videos that can be used to support the resigned education process.
With MAX, preparers have the power to make notes and take photos to personalize the consultation. Print and email capabilities empower preparers to share documents with the resigned or store in the EHR for forthcoming relation. MAX runs on iPads and is backed by Cloud-resident API services.
I',m the CTO at MAX. For over two decades, I have overseen engineering, IT operations, and fruit strategy for software and technology applications that have liberateed over $1B in value.
Desired goal
What issue was the preparer supposed to deal with?
EMBROX Solutions?We hired EMBROX to be our turnkey preparer for mobile iOS outgrowth, backend services, and to set up create and deployment infraconstruction including automation.
What were your objectives for this project?
Goals for the project were two-fold:
- Rewrite the existing application fast - in below 3 months to complete a code complete functional equiponderant running natively on iOS.
- To come in below the established budget.
Provided solution
What were the reasons for choosing ?
The vendor was selected from a list of three other vendors, interviews, portfolio examination, rates, and power to liberate.
Describe the project in detail.
The outgrowth of MAX included both the front-end and back-end rewrites. Development tasks were broken into a work breakdown construction, estimated, and organized into sprints.
Each sprint included demonstrations of progress. The demonstrations of progress included iPad demonstrations on local outgrowth devices as well as demonstrations made useful via Fabric/Crashlytics to our tester pool.
The demonstrations also included both QA and fruition environments for our full web application backend and the API services created to both read and write full for the web and mobile applications.
The API services include swagger documentation websites and test API consoles that could be authenticated over and then used.
Were there any dedicated directors or teams that you worked with?
The team was composed of a tech lead, mobile iOS Swift educeer, API/Kotlin educeer, web/front-end Javascript educeer, scrum conquer, and requirements director.
Results accomplishd
What results did you accomplish unitedly with ?
In accession to hitting the established goals, there were a couple other outcomes reached that were profitable. First, the antecedent architecture was one-resident and did not allow for cost optimizations although it was ductile based on a per client basis.
The new architecture allows for both one and multi-resident architectures and allows for cost optimizations based on really ductile calculate and storage requirements. This will lessen TCO at layer by factors of 10-100x. Second, the new architecture allows for multiple levels of authorization and administration which the antecedent solution did not hold.
Given the need to be very locked down (i.e. we are a healthcare application) having the accessional security and improved posture is a big gain and advancement.
How do you rate the interaction and interaction with ?
Triages meetings were weekly. Demonstration meetings were weekly. Backlog and sprint grooming meetings were weekly. There were inner daily scrum meetings and we participated in those when certain. The interaction was effectively handled. All team members spoke very good English and were excellent interactors.
What precisely do you attend to be the key specialty of ?
The genius of the EMBROX team was most forcible in intercourse with new technologies and the benefits they prepare (e.g. self documenting APIs and test consoles, ductileally scaling lower environments, using encrypted client-side databases). The EMBROX team is also agile and can educe fast.
What should be done better, if there are any desired advancements?
The team is little and juggles a lot of balls. One area of advancement would be in the area of limiting multitasking athwart other projects and focusing on one thing at a time to complete work without regressions and to hit specific schedules athwart all projects simultaneously.
Although the multitasking did not like our schedule negatively, there were times when interaction lagged owing of competing priorities I believe. These are expected growing pains of a little, geniused organisation as it grows in size.
