#jumboeats

[jumboeats-blog]

Post-Release Marketing Update

Now that our app is on the Android Store we want people to actually use it. Up to this point we have relied on word of mouth. We have been telling our friends about our app and what it is capable of doing. Our next step is to post on the free food Facebook pages about our apps since everyone belonging to these groups is clearly interested in finding free food at Tufts. After this, we could write posts advertising our app in the various Tufts computer science and entrepreneurism Facebook pages.

I have been asking friends to give me their impressions on the app, but to get a larger pool of opinions we could prompt users to rate the app. Chrysanthi Chaleva’s talk in class taught me a lot about best practices for getting users to rate an app. I’m thinking that we have a prompt that comes up a week after downloading the app. The language obviously should be very courteous and easy to dismiss. We think our app stands out in its simplicity. However, our review prompt could be phrased to encourage users to provide ideas for new features they would enjoy.

Our reviews as of posting this update.

[jumboeats-blog]

Week 9 Update

Kate

This week we uploaded our app to the google play store. It is an MVP, but still needs a lot of fixes, as well as the Facebook data integration. 

We are working on getting the layout of the app to be responsive on all devices, as well as the post screen to be more intuitive for users (some of our users who tested it were a bit confused on that screen). We will also need to test our app on an android device. Neither of us own one, so it has been hard to get one for testing, but we are working on it. 

We are also continuing to work on test parsing the data from Facebook, and will soon be integrating that into our node server.

What was accomplished:

App is on the play store!

Next Steps:

Responsive layout

Better post screen

More data parsing

Zach

This week I started to implement the language parsing script into the server. This is relatively straightforward, yet still presents a few challenges. First, I used jQuery to implement HTTP requests in the scripts. To make these requests work on the server I am hesitant to use jQuery since using this framework on node seems more geared towards sending web content than accessing APIs. I am using the request npm module. It’s supposed to be the simplest available HTTP module and I’ve found it quite intuitive. Next, I need to figure out exactly how the server will store the parsed posts. When writing the original scripts I just put all of the stored words in a list. Adding them to our database. 

 This coming week I want to figure out how to manage dates so we can start effectively filtering out food events that have already occurred.

I also designed the logo for our app!