Skip to main content

Posts

A user story leading to end-user and technical requirements

This post details the requirements for the game concept that we have in mind. Up next is the user story behind this app idea. User Story I want to be able to solve everyday mathematical problems mentally without using a calculator. Objective A simple game where you sharpen your math skills by answering a few quick questions. The questions can be, e.g.  7 * 8, 0.88 * 0.44 , 9 / 3 , 987 – 432, 999 + 1324 etc etc. There is no time limit to answer the question but there will be a timer that will keep track of how long before a question was answered. So that way you can see your progress at the speed of answering questions, over time. Requirements A random number generator to generate numbers. A selection of the Mathematical operation to apply to it i.e. + – * / . A selection of the number of digits for the calculation e.g. 2 = 0.83, 3 = 432, etc. A timer feature to show a ticking clock until the question is answered. Track scores! Provide a storage mechanism ...

A software engineer's perspective on product plan i.e. roadmap

A product plan is a really great method to set the long-term vision of your product (or products in my case) and set an objective to strive towards. In this post, I will just talk about my approach to creating product plans and give you an example of it. Background I have been involved in My Day To-Do for the last few years and it’s grown through the years i.e. people have come & left, downloads have almost quadrupled, user retention has increased and plenty of user feedback has been collected. This startup has had a lot of casual help the last few years i.e. contractors coming to work on a project and leaving after it’s done. E.g. an MBA grad to prepare a marketing strategy, a Chinese native marketing officer to execute the China market strategy, designers to improve the app UI, a team of translators to localise the app to 7 languages, etc etc. Among other things my duties here also involve software engineering and in the last couple of years, I had been thinking about ways...

Getting started with Firebase Analytics for iOS, Xcode app template on Github

Analytics is one of the ways in which you can know how users use your app and I think it’s very important to know how users use your app. It’s one of the things that we (or I) use at My Day To-Do (MDT) to encourage usage of certain features. What do I mean? I have written in the past that about my Software engineering background and as such my UI/UX skills are not the best. So the first think I think about when users don’t use certain features of my app is probably because they don’t know about it. Hence to compensate for that, I monitor how the app is used, so I know if the users aren’t using the features I think they should, I will add visual cues in the app to make the feature obvious for them. In almost all of the apps that I have developed at My Day To-Do, I have used Firebase Analytics to monitor app usage. In this post, I will just be talking about how to setup an iOS app with Firebase, provide some sample analytics code of the  Github repo  that I made for this...