PowerCards Week Eight Update
Last week we had our Crash Test with Elsevier, where we presented our pitch and explained more insights about our product and progress throughout the Incubation Programme.
The received feedback helped us greatly to pinpoint our strengths and weaknesses so that there is a clear path in front of us for the remaining month. We have identified that our business model needs a bit more clarification and we have to think of validating our strongest selling points. One way of doing that is via A/B testing, which we see as a great methodology to evaluate our theses and market position to our direct competitors. One more takeaway from the Crash Test is that our pitch still needs some improvements, even though the main message and idea appears much clearer to the audience in the latest, refined version.
The development of the application is ongoing at the same time as the pitch and the business model evolves. The list of features and the technologies to be used for our demo application are already clearly defined, which is essential by this point in time. The next 1-2 weeks are dedicated to adding all of the core functionality to the application, while the last step in the development will focus on testing and improving the existing functionality. Two challenges started to arise in the recent weeks, which can be interesting from the point of view of development.
On one hand, our application is very UX-oriented and includes many features on the user interface level, such as drag & drop, gesture recognition, animations, handling images and shapes. This is something that our CTO has not worked with before. Despite the unfamiliarity with the available tools, good progress is being made, but more importantly, this should be seen as a great possibility for learning something new. The other challenge is about time management and allocation of resources. Programming is commonly seen as a mentally challenging problem-solving task, which consumes lots of energy from the developers. Being a mentally tiring task to perform, some say that usually less coding is more, because a tired coder is likely to make more mistakes in their work, which will cost more in the long run. As our CTO is a software developer in his daily job, it is rather challenging to keep being focused on multiple projects after 7-8 hours of coding.
On the other hand, we would like to conduct testing experiments to gather hands-on knowledge of our work by the demo day. Fortunately, the TestFlight service provided by Apple is a great tool, which can help us with the former. Through this ecosystem we will be able to easily distribute the alpha version of our application to those volunteers, who have given their e-mail address to us during our market study at the beginning of the programme. Via this service, they will be able to download our application with a single tap of a button. Ultimately, users can easily provide us with feedback on the look & feel of the application and propose improvements to the whole package. Along with this pipeline, we aim to conduct A/B tests with a selected set of medical students, who will perform the same tasks in PowerCards and competitor applications. This way we can pinpoint areas where there is room for improvement and gather direct feedback from our targeted audience.