{"action":"created","issue":{"url":"https://api.github.com/repos/rackt/react-router/issues/743","labels_url":"https://api.github.com/repos/rackt/react-router/issues/743/labels{/name}","comments_url":"https://api.github.com/repos/rackt/react-router/issues/743/comments","events_url":"https://api.github.com/repos/rackt/react-router/issues/743/events","html_url":"https://github.com/rackt/react-router/issues/743","id":56110481,"number":743,"title":"React Native","user":{"login":"ryanflorence","id":100200,"avatar_url":"https://avatars.githubusercontent.com/u/100200?v=3","gravatar_id":"","url":"https://api.github.com/users/ryanflorence","html_url":"https://github.com/ryanflorence","followers_url":"https://api.github.com/users/ryanflorence/followers","following_url":"https://api.github.com/users/ryanflorence/following{/other_user}","gists_url":"https://api.github.com/users/ryanflorence/gists{/gist_id}","starred_url":"https://api.github.com/users/ryanflorence/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ryanflorence/subscriptions","organizations_url":"https://api.github.com/users/ryanflorence/orgs","repos_url":"https://api.github.com/users/ryanflorence/repos","events_url":"https://api.github.com/users/ryanflorence/events{/privacy}","received_events_url":"https://api.github.com/users/ryanflorence/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/rackt/react-router/labels/discussion","name":"discussion","color":"5319e7"},{"url":"https://api.github.com/repos/rackt/react-router/labels/react-native","name":"react-native","color":"207de5"},{"url":"https://api.github.com/repos/rackt/react-router/labels/revisit-after-1.0","name":"revisit-after-1.0","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":42,"created_at":"2015-01-31T03:24:09Z","updated_at":"2015-11-07T22:10:53Z","closed_at":null,"body":"Just tracking react native thoughts here. My assumptions are probably all wrong since 1) I don't know much about native dev and 2) I've spent 5 minutes with react native but:\r\n\r\n1. Looks like a component is mounted as the \"top level\" thing, the router listens to a location and then renders an app, so the basic usage is probably going to be slightly different, your top level component has route definitions and gets a url passed in as a prop or something.\r\n\r\n2. We need some sort of iOS `Location` and eventually an `Android` location, it'll probably be stored in memory and persisted to some sort of `localStorage` equivalent. When the app boots we look at the URI requesting the launch first, and then the `localStorage` (whatever it really is) second.\r\n\r\nAgain, I have no idea what I'm talking about yet. ¯\\(º_o)/¯"},"comment":{"url":"https://api.github.com/repos/rackt/react-router/issues/comments/154757481","html_url":"https://github.com/rackt/react-router/issues/743#issuecomment-154757481","issue_url":"https://api.github.com/repos/rackt/react-router/issues/743","id":154757481,"user":{"login":"skevy","id":131916,"avatar_url":"https://avatars.githubusercontent.com/u/131916?v=3","gravatar_id":"","url":"https://api.github.com/users/skevy","html_url":"https://github.com/skevy","followers_url":"https://api.github.com/users/skevy/followers","following_url":"https://api.github.com/users/skevy/following{/other_user}","gists_url":"https://api.github.com/users/skevy/gists{/gist_id}","starred_url":"https://api.github.com/users/skevy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/skevy/subscriptions","organizations_url":"https://api.github.com/users/skevy/orgs","repos_url":"https://api.github.com/users/skevy/repos","events_url":"https://api.github.com/users/skevy/events{/privacy}","received_events_url":"https://api.github.com/users/skevy/received_events","type":"User","site_admin":false},"created_at":"2015-11-07T22:10:52Z","updated_at":"2015-11-07T22:10:52Z","body":"Yah that could work, though it would be great if the user didn't have to care whether or not they were pushing to the parent navigator or not.\r\n\r\nIt would be awesome if when you did \"this.context.history.push\" -- it would just go to wherever it needed in the app, no matter where you are (this would be the whole \"bringing web semantics to native\" thing).\r\n\r\nBut then \"this.context.history.goBack\" is more difficult...because you don't _usually_ want to go back to some arbitrary route in your application (though I can see times when you would want to do that)...you usually want to pop the most recent view off the current navigator. Maybe it's in this case where the user of the API _does_ have to concern themselves with their current nesting...and whether or not they want to \"go back\" in the context of the app, or \"go back\" in the context of their current nested `Navigator`."}}