- Fan Website and Code Academy (http://ima.nyu.sh/documentation/2017/02/22/fan-website-and-code-academy/)
- Video Embedding (http://ima.nyu.sh/documentation/2017/03/08/video-embedding-by-tyler-rhorick/)
- Giphy Galaxy (API Assignment) (http://ima.nyu.sh/documentation/2017/04/26/giphy-galaxy-by-tyler-rhorick-developing-web-api-assignment/)
Reflection: After having completed all of the assigned CodeAcademy, I must say that there are real serious pros and cons to these lessons. One of the biggest pros I would say in using these lessons was a development of base understanding. After having done all of these lessons, I can confidently say that I can look at a section of code and have an idea of what is happening in the code. With that said, I wish these lessons had more practical examples. Often the courses make you do a task that seems pointless because it would not be used that commonly in practice. For instance, there was one memorable part where they were trying to force me to make a counting function. I thought that having more useful examples would be helpful.
For my responsive website, I decided to make a responsive portfolio, since this was going to be a requirement for my senior capstone. Drawn to dark colors that would allow the vibrancy of my work to stand out, I decided to go with a black and grey theme. Also, in order to get a good understanding of how to code the website, I avoided any frameworks like bootstrap, etc. Here is what the current website looks like on a larger browser:
And here is how it comes responsive:
After receiving feedback, I decided that I needed to do a better job at figuring out the spacing and design of the top header, since many people thought it might be confusing. I also got recommended to maybe include a bit of color and that the pictures might look better without the borders. With these critiques I decided to make modifications and created what in the end became my portfolio shown below:
The original project can be accessed on the NYU server at http://192.168.50.184/~tpr226/responsiveport/
And my finalized capstone portfolio can be seen at https://trhorick.github.io/
Final Project Documentation:
Project: pauseWatch app
Website Link: http://web.nyu.sh/pausewatch/start.html
Tyler Rhorick and Rewant Prakash
Project description: pauseWatch is an assistive technology device for people with mental disorder. The interface for pauseWatch relies on using different sensors and arduino mkr1000 to calculate body vitals, and if the body vitals are not in range, it triggers an api that redirects users to a web app that helps them calm down.
This app, for the time being, allows the user to be redirected to two different youtube playlists– 1. The Meditation playlist, 2. Humor playlists. When the playlists are triggered, the app shuffles the songs in the playlist, giving its users access to different order of playlist every time. Furthermore, the app also triggers a email to someone the user designates while setting up this app, giving users a lot of accessibility and variety of options based on their personal preference.
Pushingbox API, pushbullet API, arduino mkr1000, php server and youtube embedding
Ideation & prototyping:
We first came up with idea to develop pauseWatch app while discussing the possible future impact of pauseWatch. pauseWatch interface relies on using several different APIs such as pushingbox API, pushbullet API, and IFTTT API. While the APIs were successful in performing the intended functions, we wanted to give users option to choose their preference and interaction when they first set up the app, instead of the different APIs functioning independently. We believe that any or every user has the ability to make their own decisions, therefore we wanted to give the users an option to set their preference single or multiple times.
In our current design, the user downloads the app and sets up their user preferences. These preferences allow the user to input their name, the emails they wish to be notified if their pauseWatch is activated, and the frequency that they would be asked how they would like to de-stress (once or every time the watch is activated).
Once the pauseWatch app is setup the user is ready to use their pauseWatch. After the pauseWatch app is set up, their pauseWatch watch will monitor the user’s vitals when they wear it. Looking for an increase in temperature and heart-rate, the pauseWatch will activate when these vitals indicate that the user might be stressed out. Encouraging the user to take a pause and relax, the pauseWatch will interact with the pushbullet API to send a phone notification to the user. This phone notification will link the user to the pauseWatch app, which will respond to the user’s chosen settings and send the required emails upon opening. If the user has chosen to pick how they would like to destress every time, they will get to pick how they want to destress with pushbuttons that will link to options to de-stress.
Otherwise, if the user picked to just be asked once how they’d like to de-stress, it will go to the page related to how they want to destress. Once on the page related to how they should de-stress, they will see a randomly generated youtube video related to their prefered way of destressing.
While building this app, we had a few challenges.
- Php to send email to a designated user
- One of our biggest problems was trying to figure out why our PHP code wasn’t working to send emails to the users. We ended up figuring out that the problem was because we were hosting our pages locally. After talking to Matt, we got the email functionality to work when the website is hosted on the IMA webpage, but a current issue is still with the string parsing. We want to look back in this more detail soon to see if we can remedy these issues.
- Responsive youtube embedding
- pauseWatch device integration with the app
- More variety of content in the app
- Using push notification triggers and redirections from the app itself
- Launching an app on google play store/ ios app store
What I enjoy most about working on this project is how it was able to use everything we learned in class. From incorporating our lesson on forms, to mobile and responsive websites, php, and connecting a website to an arduino, I think we accomplished a lot with this project. In the end, I think our project is commendable because it works and is a valuable asset to Rewant’s capstone project. What I think may need to be improved in later iterations is the design. One thing that we didn’t talk about in class that I might have wanted to discuss more is how to make an appealing phone app. We chose to go for a simple look to not overcrowd the space on the phone, but I question if this is the best decision. Should we have added more? What design elements could we have changed. I think another thing that was an important lesson I learned from this project was the limitations of hosting a website locally. I feel like often times when things don’t work out I automatically assume it must be something in the code I wrote. What this taught me is that with web development it is also important to look at the way you are using the code to make sure that it is actually the code that is the problem and not the permissions. Overall, it was a great project as my last project in IMA and I had a great time working with Rewant, which is something I suprising hadn’t gotten to do yet in IMA.