We know how much this will assist them in their day to day work and the technical requirements of such a system do not require any new technology beyond what many apps already utilise. The price point that many people termed as ‘easily affordable’ on our surveys will hopefully allow us stay profitable and make our product accessible to even new entrants to the profession and students. This assumption will remain true even if only 10% become paying customers. Our ability to keep it that low will be re-assessed after hiring decisions and technology requirements have been ascertained.
We do not intend to use third party analytics or include any kind of advertising, and will not be selling user data for any reason.
I have been in the industry for 15 years and have extensive personal experience of the job we do and how such a product would cut down on time wasted while improving efficiency and productivity.
While I am not a technical person, I did spend some time learning and do understand some basics about UI & UX design, software architecture and software development life cycle. The limit of my technical education was HTML, CSS and JavaScript that I’m not entirely proficient with.
I want our product to be easily maintainable, reliable, scalable and fast. I don’t want to have a small set of early employees who know everything and then any new people would struggle to understand what they did after they’re gone especially if they leave abruptly. I don’t want code that is difficult for a colleague or subsequent employee to update and improve. I don’t want a product that’s slow and frustrating to end users. I don’t want a product that requires too much education for a basic non-techie person to use comfortably. I also don’t want a structure that doesn’t scale as users grow beyond the small subset we are beginning with since the product may be relevant to other industries beyond the initial one I am focused on.
Our budget is significant but not open ended so I also want to have all of these expectations met as reasonably as possible.
I have several advisers and one is a CTO at a major tech company and he would be helping me with the hiring process for the engineers. I will not be sitting through those conversations mindlessly or just nodding along so I want to know what questions I should ask and what aspects of our relationship need definition so that these expectations are met and I’m not at risk of dealing with the same problems I’m actively trying to avoid or requiring a full-rebuild after a short while.
We are building an app for iOS and android and the web portal will allow users manage their accounts/payments and also allow for admin access to continually update the app’s content.
Also, document your use cases with something like this: https://creately.com/
Design System:
https://uxdesign.cc/everything-you-need-to-know-about-design...
https://www.figma.com/design-systems/
Graph API: