desmondmc / roomease Goto Github PK

We need a way to invite people and let them know about the app. For example, I could invite Jim to join the house and he would get a notification that would then prompt him to download the app and join my house.

The roommate view flashes a couple times when it's refreshing. Is it pulling the roommates more than once? Need to look into this.

It would be amazing if we could run some code when the location services settings are changed. Not sure if this is possible. With some quick testing it seems didChangeAuthorizationStatus is only called when the app reopens after a change. This kind of sucks.

Figure out why Jillian's phone won't get out of the unknown state.

It would be nice if we stored the reason a user's location was set to unknown. Whether it be because they are running iOS 7.0 and they haven't checked in in a while, they have location services turned off, or they don't have an address set.
We could use this data to debug as well as show the user.

They are pixelated. Higher PPI?

Right now we just assume everyone will allow location services. What if they don't?

Seems like there is an issue adding channels to a user when they login and out of different houses.

Rhys, you said there might be someone that can help us out. Here's a issue to track that action.

There should be a setting in config that turns off alert notifications for the app. Just incase people get annoyed of being told anytime a roommate arrives or leaves the house.

In the meeting you had a lot of issues with the website. What could we change? Feel free to take the source code and make whatever changes you want to it. Maybe your developer friend can help?

Every time the user opens the main view we should update the users location.

If the currentUser is in the process of being saved when a logout occurs the app can crash. Saving the current user should lock the UI until success or failure occurs.

There should be two functions added in a central place.

• One that gets called everytime the user logs in. Put all general setup stuff here. (Notification channels etc.)
• One that gets called only the first time a user joins a house.

Seems like users who turn off wifi experience weird behaviour with the 'at home' feature (app isn't notifying the server when the person leaves home, pushes are being sent to house members saying 'User arrived home' + 'User left home' in a short period of time).

We need to further test this issue and diagnose what exactly the problem is and our best options for solving it.

Right now the settings page is just something i threw together for testing. It looks like crap. We should talk about all the functions that need to be in the settings and come up with a nice looking design for it.

Off the top of my head we need:

• House location setting
• Change profile Picture

Make sure we confirm with the user that they want to delete a list item!

To do this we'll need to make a sliding view. Also if there are less than 4 roommates the images should be evenly placed atop the bar.

It would be super cool if the app allowed you to turn off notification for a specific user. People can choose to only be notified by one/any number of roommates.

It's ugly right now.

Greg and I have done a lot of this. Is it totally done?

The default functionality for notifications should be that the user receives notifications from all users in the house, but can disable them if they want to (not the other way around). This avoids the scenario where the user doesn't know they need to subscribe to get notifications and they miss out on the feature.

Right now you have to take a selfie on site. Allow users to be able to pick a photo from their library.

Right now, especially if a user is running 7.1 their status will be stuck in whatever they logged out in.

As a user, I would like to be able to "Watch" other people's houses. The user wouldn't get notifications when users com home/leave but could check if people are home or not. So the user wouldn't get full info/functionality like someone who actually lives in the house, but could check if their friends are home or not.

Maybe we should add a status bar or something. Also roommates should resync after the upload is done.

When a new user joins a house I am already a part of, I should get a push notification (if the app is closed) or a pop-up (if I already have the app open).

The app is filled with warnings. We need to go through the code and clean them all up.

The app is going to allow users to select which roommates they receive push notifications from. My thought is that the can click a profile picture and turn on and off push notifications for that user. Haven't fully thought out how to display it.

What do you think Erik?

Whiteboard exactly when location information is changed and how we should communicate that to the app and the server. It's starting to turn into a mess.

Adam: It Couldn't find Stittsville on the map unless I put Ontario after it.

Location finder needs to be rethought.

Title says it all.

We should only send a push to update if critical UI data changes. Otherwise there is no reason to send the push.

When the "Refresh Roommates" button is clicked, there should be a loading icon to let the user know that code is running. Otherwise they may keep jamming the button causing a lot of network traffic to start. This way they know to wait and that something is happening.

The height of the ToDo list cells are based on the width of the delete button. The bigger the button the bigger the cell. Send me a larger delete button and i'll make the cells taller.

Pull down? Or maybe just not have one.

Have the signup page have some cool modern artsy image in the background. Kind of like this!

http://pttrns.com/p/325

We should notify the members of a house with a push notification when someone new joins it.

#21

Right now it's grey, could be nicer.

If a new user joins a house while the app is backgrounded they aren't added to top view when the user opens the app. Even running refresh roommate doesn't add the extra user. Probably something to do with Central Data?

It seems like if there are a lot of people in a house. Push notificaitons aren't getting sent/delivered to everyone. It makes more sense if all the heavy lifting is done in the cloud.

We need to tell the user if background app refresh is off we can't access their location.

When a user is logged out we no longer track their whereabout. We should set their location to unknown.

The app needs to be tested for offline use. Right now all development has been done with an internet connection. What if the user has a bad connection or loses it while in the app. We need to have a story for this.

Seems it's possible for the aftersave function on House objects to take more than 3 seconds and time out. Greg and I saw a crash where this happened.

It seems that the callback:

- (void)locationManager:(CLLocationManager *)manager
      didDetermineState:(CLRegionState)state forRegion:(CLRegion *)region

Is not always called when we request the state for the current region:

[self.locationManager requestStateForRegion:region];

Seems to only work 40-60% of the time when the app is coming to the foreground but works better when the app is already in the foreground and "Refresh Roommates" is pressed (90%).

Thought it might be that ARC is cleaning up the location manager but with some quick investigation that doesn't seem to be the case. Not sure why this is happening.

Find every bug that exists when tracking if a user is home or not. This is a pain in the ass to test but someone needs to do it.