{"action":"created","issue":{"url":"https://api.github.com/repos/webcatalog/webcatalog/issues/29","repository_url":"https://api.github.com/repos/webcatalog/webcatalog","labels_url":"https://api.github.com/repos/webcatalog/webcatalog/issues/29/labels{/name}","comments_url":"https://api.github.com/repos/webcatalog/webcatalog/issues/29/comments","events_url":"https://api.github.com/repos/webcatalog/webcatalog/issues/29/events","html_url":"https://github.com/webcatalog/webcatalog/issues/29","id":304669839,"number":29,"title":"Distinguish single-page apps from ordinary websites","user":{"login":"Erudition","id":3915447,"avatar_url":"https://avatars2.githubusercontent.com/u/3915447?v=4","gravatar_id":"","url":"https://api.github.com/users/Erudition","html_url":"https://github.com/Erudition","followers_url":"https://api.github.com/users/Erudition/followers","following_url":"https://api.github.com/users/Erudition/following{/other_user}","gists_url":"https://api.github.com/users/Erudition/gists{/gist_id}","starred_url":"https://api.github.com/users/Erudition/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Erudition/subscriptions","organizations_url":"https://api.github.com/users/Erudition/orgs","repos_url":"https://api.github.com/users/Erudition/repos","events_url":"https://api.github.com/users/Erudition/events{/privacy}","received_events_url":"https://api.github.com/users/Erudition/received_events","type":"User","site_admin":false},"labels":[{"id":850839521,"url":"https://api.github.com/repos/webcatalog/webcatalog/labels/enhancement","name":"enhancement","color":"a2eeef","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-03-13T08:35:03Z","updated_at":"2018-05-15T17:09:49Z","closed_at":null,"author_association":"NONE","body":"Hi! New contributor here - great project.\r\n# Problem\r\nAlthough SSBs can be used for browsing any old website, even one that has an app-like aesthetic, users such as myself (and I assume many others) just want them for actual _Web Applications_ - typically a single, JS-heavy page.\r\n\r\n**Example of a true Web App**\r\nMessenger.com\r\n\r\n**Example of a... web site**\r\nKickstarter.com\r\n\r\nWhile these both have Material design feels, the former is clearly a single-page web app (just like its native mobile counterpart) while the latter is a live listing of projects on a website that all have dedicated pages.\r\n\r\n\r\n# Rationale\r\nI personally would never really want to containerize the latter not just because I wouldn't see as much of a need to leave it open all the time,  but also because the lack of browser chrome is actually a hindrance in that case - and the isolation of the app conveys little benefits. \r\n\r\n### Examples\r\nOn Kickstarter you are highly likely, for example, to encounter external links. In a browser you would simply open a new tab without launching another application (annoying to do a lot) because it belonged there in the first place. You would likely want to browse multiple projects at a time, which is what the browser's tab interface was made for. On Messenger, though, the only \"tab-able\" content is already in a conveniently tabbable format. There is little reason to have multiple instances of it (which can cause issues anyway). There is an obvious reason to leave it open indefinitely.\r\n\r\n# Solutions\r\n## Tags and filters\r\nI'm sure some people will disagree with me so rather than ditching these allegedly non-app items altogether what if we could hide them from the catalog? In this case I would suggest a tagging system and an option to filter the catalog by tags."},"comment":{"url":"https://api.github.com/repos/webcatalog/webcatalog/issues/comments/389242727","html_url":"https://github.com/webcatalog/webcatalog/issues/29#issuecomment-389242727","issue_url":"https://api.github.com/repos/webcatalog/webcatalog/issues/29","id":389242727,"user":{"login":"nblackburn","id":2931085,"avatar_url":"https://avatars2.githubusercontent.com/u/2931085?v=4","gravatar_id":"","url":"https://api.github.com/users/nblackburn","html_url":"https://github.com/nblackburn","followers_url":"https://api.github.com/users/nblackburn/followers","following_url":"https://api.github.com/users/nblackburn/following{/other_user}","gists_url":"https://api.github.com/users/nblackburn/gists{/gist_id}","starred_url":"https://api.github.com/users/nblackburn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nblackburn/subscriptions","organizations_url":"https://api.github.com/users/nblackburn/orgs","repos_url":"https://api.github.com/users/nblackburn/repos","events_url":"https://api.github.com/users/nblackburn/events{/privacy}","received_events_url":"https://api.github.com/users/nblackburn/received_events","type":"User","site_admin":false},"created_at":"2018-05-15T17:09:49Z","updated_at":"2018-05-15T17:09:49Z","author_association":"CONTRIBUTOR","body":"@quanglam2807 That is a tricky one that i think more than 1 person needs to answer.\r\n\r\n> The primary purpose of a website is to convay information where as a application is there to interact with information.\r\n"}}
{"actor":{"display_login":"nblackburn"}}