Hello blog viewers,
Did you know that stress in known as ‘the silent killer’? It can result in heart disease, stroke, obesity, depression, and other health problems.
-Source: Web M.D.
I have just completed the second week of my SRP. During this week, I researched about common sources of stress, how to measure stress (which will aid me in focusing on the content in my app design), and how I can convert answers to numbers which I can use to compile data which will be displayed on graphs. I still have to research a lot more before I can figure out how I will transform qualitative questions to quantitative analytics.
Speaking of the graphs, I was thinking of the best types of graphs to use, to display the user’s stress information. I decided to have -- at the minimum -- a pie graph or a bar graph (to show the most common stress triggers experienced by the user), line graphs (to show when and where the user was stressed), and a bar graph which scales how high the user’s stress levels were for the duration that the data was entered.
I also made the basic framework of the app which I will build upon in the next few weeks. This basic framework includes creating the stress button (which users can tap whenever they feel stressed), setting up the basic view controllers in each of the four tabs of the app (discussed in my week one post), and setting up a table view for the settings tab.
This image shows an example of a tableview (which the settings tab will have). This view will allow for the best user interface for the settings. The other tabs will not necessarily use this view; they will use buttons, labels, and images to display information and questions.
While I was starting to make the basic framework for the app, I ran into one big problem in Xcode, where Xcode thought each of my newly created View Controllers had a header file (.h file which is used in Objective-C coding) instead of a swift file (.swift which is used in Swift coding, hence the name). Once I resolved this issue, coding was much smoother and I successfully coded the tab view controller logic (conditional -- if else -- statements).
I plan on completing the the basic framework for each of the four tabs by the end of next week. This will include basic functions in each of the tabs. I will also work on making the app look better aesthetically (since it is just a plain white background with blue buttons and labels at the moment).
I hope to see you all in my next blog post!
It's so cool to see the progress you're making with your project. I'm really interested in seeing how your framework turns out.
ReplyDeleteWhen I used to work with clients in a therapeutic setting, I was always surprised to find that when I asked the question, "How often are you stressed, and when?" they did not know the answer, making it even more difficult to manage their stress. Your app could be extremely helpful in this setting, helping clients to determine when they feel stressed and how this stress presents itself, and then being able to provide this information to their therapist or physician to create an effective treatment plan.
ReplyDeleteHave you thought about the vocabulary you will use? Will you provide a list of symptoms? For example, what one person might describe as "muscle aches" another person might describe as "sore".
Nice progress Saif! Do you know what it'll look like when it's all done (colors, etc)?
ReplyDeleteThis looks great! Once the app is done do you plan on putting this app on the android app store too?
ReplyDeleteYou are make good progress. I am looking forward to how your investigations into wording of the question and converting possible qualitative answers to numerical data play out. And of course, I cannot wait to see all of the graphs!
ReplyDeleteLooks like you really got a lot done this week Saif! How does the number produced correlate to stress level? Is it the higher the number the more stressed you are?
ReplyDelete