{"action":"created","issue":{"url":"https://api.github.com/repos/inaturalist/INaturalistIOS/issues/240","labels_url":"https://api.github.com/repos/inaturalist/INaturalistIOS/issues/240/labels{/name}","comments_url":"https://api.github.com/repos/inaturalist/INaturalistIOS/issues/240/comments","events_url":"https://api.github.com/repos/inaturalist/INaturalistIOS/issues/240/events","html_url":"https://github.com/inaturalist/INaturalistIOS/issues/240","id":126994772,"number":240,"title":"Projects Section 2.0 Functional spec","user":{"login":"joellebel","id":11527994,"avatar_url":"https://avatars.githubusercontent.com/u/11527994?v=3","gravatar_id":"","url":"https://api.github.com/users/joellebel","html_url":"https://github.com/joellebel","followers_url":"https://api.github.com/users/joellebel/followers","following_url":"https://api.github.com/users/joellebel/following{/other_user}","gists_url":"https://api.github.com/users/joellebel/gists{/gist_id}","starred_url":"https://api.github.com/users/joellebel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joellebel/subscriptions","organizations_url":"https://api.github.com/users/joellebel/orgs","repos_url":"https://api.github.com/users/joellebel/repos","events_url":"https://api.github.com/users/joellebel/events{/privacy}","received_events_url":"https://api.github.com/users/joellebel/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/inaturalist/INaturalistIOS/labels/Design","name":"Design","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-01-16T02:26:30Z","updated_at":"2016-01-20T19:02:42Z","closed_at":null,"body":"All Functional specs are contained in the below google doc. Please leave all comments/questions in this issue. \r\n\r\nhttps://docs.google.com/document/d/1uKSVmMRBFKf9nLRRcSlVj4dG2z0yPjZMfn2GL3KpVVw/edit?usp=sharing"},"comment":{"url":"https://api.github.com/repos/inaturalist/INaturalistIOS/issues/comments/173325723","html_url":"https://github.com/inaturalist/INaturalistIOS/issues/240#issuecomment-173325723","issue_url":"https://api.github.com/repos/inaturalist/INaturalistIOS/issues/240","id":173325723,"user":{"login":"joellebel","id":11527994,"avatar_url":"https://avatars.githubusercontent.com/u/11527994?v=3","gravatar_id":"","url":"https://api.github.com/users/joellebel","html_url":"https://github.com/joellebel","followers_url":"https://api.github.com/users/joellebel/followers","following_url":"https://api.github.com/users/joellebel/following{/other_user}","gists_url":"https://api.github.com/users/joellebel/gists{/gist_id}","starred_url":"https://api.github.com/users/joellebel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joellebel/subscriptions","organizations_url":"https://api.github.com/users/joellebel/orgs","repos_url":"https://api.github.com/users/joellebel/repos","events_url":"https://api.github.com/users/joellebel/events{/privacy}","received_events_url":"https://api.github.com/users/joellebel/received_events","type":"User","site_admin":false},"created_at":"2016-01-20T19:02:42Z","updated_at":"2016-01-20T19:02:42Z","body":"For the Projects list I would think you could still see them even if you're not logged in so you can get a sense of them find them as one more reason to sign up for iNat. When attempting to join one and not logged in the user can get a prompt to sign up/log in. If the user has not accepted app location permissions when they go to the Nearby toggle, they would get the location permission prompt.\r\n\r\n> Project posts on the web can have comments. Are we going to support them on iOS?\r\n\r\nFrom a user standpoint I think it would be informative to see the comments and even more engaging to be able to comment. From an engineering standpoint how complicated is this? As for the UX of the commenting flow I would envision comments appearing below the post and there would be a comment button which would activate a flow similar to that of the Activity Tab commenting flow.  If this is something that can be implemented and we all think it's a good idea. I can design it. \r\n\r\n> What happens when you tap the \"Start Browsing\" button on the No Projects version of the page?\r\n\r\nWas thinking it would put you in the Featured tab. \r\n\r\n\r\n> The current implementation of the project list view has a pull to search. Is that expected to be in this version as well? If so, how do you think it should function?\r\n\r\nI think it's confusing to the user that the search is not limited to the active segment. Originally, I was trying to change as little as possible with this section due to the deadline. \r\n\r\nQuestion: Do we need that refresh button in the navbar? If not, we could put a search button up there since the current search functionality isn't faceted anyways. Later on we can add a more sophisticated search if needed or a scope bar. This would also make it easier on project admins when informing users how to find their projects. They could simply say \"Go to the Projects section (in the More tab) and search for \"Project X\". \r\n\r\n\r\n> Since the featured projects section will include some nearby projects, do we still need the nearby project section?\r\n\r\nI vote to keep to keep nearby projects so users can quickly see their nearby projects. For now there will be a lot of overlapping, but in the future featured projects may be expanded. \r\n\r\n\r\n> Some stuff that would be nice to show in the project info screen instead of just description text: project curators/managers/admins/creator, creation date, terms, associated place, field requirements.\r\n\r\nTotally agree, but again was going for MVP for the first version and see these as enhancements that can come down the road. For now, I would love to keep it opening in a screen (as opposed to a pop up modal) and this screen will definitely evolve.\r\n\r\n\r\n> At what point will users be joined to these projects? During account creation? Or when they first visit the project or news page?\r\n\r\nI'm assuming they will not be able to see projects like NPS or OOTW unless they have joined it? It would be nice to be able to see these without having joined them, but I realize this may complicate things for now. I was thinking they would see these news posts after creating an account and we will be automatically joining them to NPS, OOTW, OOTD and Critter Calendar upon account creation. (It's still yet to be determined what we're doing for legacy users) \r\n\r\n\r\n> That last comment raises another question for me: what do we do for users who haven't logged in yet? In the current public release, we don't show the projects part of the app until they signed in.\r\n\r\n\r\n\r\n> In the not-logged-in case, what do we show for the news list view? How about the project list view(s)?\r\n\r\nI'll mock up the signed out state for news list because since you're signed up/logged in, you're \"not a part of\" any projects and therefore cannot see their news posts. \r\n\r\n\r\nWill get to any comments I have left out."}}