Initially we debugged with lint through the Android App Studio’s native inspect tool. We were able to catch hard-coded values, unused dependencies and many similar issues. In order to generate the report we then began to test from the command line. This provided us with tons of warnings and initially 62 errors, as can be seen in our initial report. However, the errors stemmed from what seems to be a bug in lint and we were able to resolve them through the lint.xml file in the project’s root directory. As of right now, there are no lint errors in our project. Moving forward we are definitely going to address many of the errors in the lint report. The reason that the ones that are there now are because we have not had success running the emulator on later versions of the Google Play Store so we have tons of out of date warnings. We also have unused resources that we will need soon on a few of our views that we are currently working on.


Espresso is used to do UI testing, meaning it simulates the actions actually performed by the user and makes assertions about how the app responds. We wanted to do this because it is the most detached way of testing… it doesn’t matter if junit tests indicate the backend is working if something the user is trying will not work. We built a test that will testing the logic of the post listing view. The idea of this page is that if a listing already exists at an address then a user cannot post another. In our test, the user tests this out then successfully posts an app.


Installing Crashlytics was a snap. Fabric provides visual, step-by-step instructions within the plug-in. Our first crash report can be found here.

User Interviews

We interviewed two of our housemates, both of whom have had previous experiences (both positive and negative) in finding off-campus housing. Here are our main takeaways based on both their explicit feedback and general navigation of the app.

  1. iOS users are not aware of the back navigation button on Android devices, which may make it useful to supply this feature redundantly within the app’s UI itself. Both users had to ask how to return to the main activity from the listings page.
  2. Posting a listing is not seen as a useful feature, which brings up the current lack of incentive for current tenants to participate in the following year’s lease agreement. This will likely continue to be beyond the scope of our app this semester, although it sparked an interesting conversation regarding the possibility of creating contracts between landlords and their current tenants to circumvent the use of a realtor.
  3. Having reviews, and having those reviews be made from Tufts students authenticated via email address, would add to the listing’s legitimacy.
  4.  Users expect the info window that appears upon clicking on a map marker to have more information, and to be clickable itself. There was expressed interest for pictures of the listings and how many other students were currently looking at a given listing.




Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s