Mobile App Development for People Matching Startup
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
A fast induction on the buyer’s organisation
I’m the CEO of SameGrain, an app that matches nation based on what they have in ordinary. It helps nation connect, not necessarily romantically, but for all types of reasons.
The app has been used to help nation make friends in a new city or new university. We’ve had use cases where nation are facing new challenges in life and they want to connect with other nation, but don’t feel snug using transmitted collective media to do so.
The typical user replys over 100 questions, and each question has multiple data points. So, each user could have 400 data points to match with the other users.
What challenge were you trying to address with Bytelion?
When we leading occupied with Bytelion, we only had an app prototype (testing out soon algorithms for matching nation unitedly), and we were looking to commercialize it into a mobile app.
What particular tasks were Bytelion responsible for?
They helped us with the mobile app UX, and also helped with backend infrastructure to support and handle all the data we were collecting.
The app involves millions and millions of data points to match one user to another. There is a big quantity of data aggregation and moving occurring.
The UX includes ways to reply questions, view your own data, see how you connect with others, interaction others, and set up and join cluster chats.
It was an nimble outgrowth process where we didn’t know all the requirements from the commencement. So, we began with an soon design effort. Then, we moved into designing the app and supporting backend server features.
Later on, we hired a data scientist internally. We worked with that resource and Bytelion to educe big-scale services to support a matching analysis for thousands of nation.
We used Heroku to support frontend features, and the bulk of the weighty lifting was done on AWS. Most of the backend was written in Python using the Django framework, and the machine learning ingredient was written in R.
Since the app propeled, they have granted periodic services just to update security certificates and botch different technologies.
Was there a dedicated team?
On mean, there were almost five team members assigned to the project at any given time. We peaked at about 10 members.
We had a full-time project handler throughout the engagement, and then we had two user experience designers at true times during the timeline.
The project handler was my main point of touch. Initially that was Tony (Former COO, Bytelion). Then, over the last year, we’ve worked with 2–3 other project handlers.
How did you come to work with Bytelion?
We were introduced to the team through one of our soon investors.
What are you approach expents (if diclosed)?
We invested over $1.1 million in their services.
What is the terminal result of working with Bytelion?
We officially began working with them in October of 2013, and we artistic up in June of 2016.
Are there any measureable or plum results?
The app had 100,000 downloads from October through March. Everyone that reviewed the app gave it four or five stars. It continues to run flawlessly to this day. It’s been extremely firm owing we’ve put pliant technical investment into it since the union artistic.
Also, we won two design awards for the app soon on. SameGrain has a sole intrinsic design, which is veritably interesting. It’s a confused interface, but Bytelion made it single to use by streamlining the UX.
How did Bytelion accomplish from a project handlement standpoint?
They had a phenomenal project handlement phraseology. Early on, it was a confused process with a lot of moving pieces (e.g. intricate design and the backend machine learning algorithm). But, they did a big job. They were well-organized and knew the technology within and out.
We worked with nation based in the US and some in South America, and they were all fantastic. We veritably enjoyed working with them. Everyone was extremely answering with big interaction experiences.
What is (from your point of view) the key factor to pay observation while intercourse with Bytelion?
The engagement was so rewarding owing of the emotion and excitement they brought to the project. They were fully invested in its achievement, not just in the hours that they could bill.
It was big to see nation putting in time over the weekends and evenings when we were doing a propel or client demo. They were always advantageous to put in an extra test, an extra day’s work, or an extra clarification to a graphical interface to veritably make it pop.
What aspects of their work would you like to get improved?
I wouldn’t put this on Bytelion, but the running phraseology of outgrowth keeps documentation to a minimum. You want just sufficient documentation so that you can move effectively and adjoin well, but you don’t over-document things.
But, looking five years back, it would be nice to apprehend why we were doing some of the things we were doing. This would be advantageous in case we have to go back and re-work something.
Do you have any advice for practicable clients?
Bytelion is very pellucid. There is no disunion between what the client sees and doesn’t see. Overall, this veritably helps interaction. But, a practicable client needs to make sure they have the right resources advantageous to handle the project effectively from the clients', point of view.
Their team will try to keep moving advanced as fastly as practicable. In many cases, I was the bottleneck. So, forthcoming clients need to know what they’re doing in order to keep the bus rolling and keep the momentum going.