{"action":"opened","issue":{"url":"https://api.github.com/repos/lionheart/openradar-mirror/issues/480","labels_url":"https://api.github.com/repos/lionheart/openradar-mirror/issues/480/labels{/name}","comments_url":"https://api.github.com/repos/lionheart/openradar-mirror/issues/480/comments","events_url":"https://api.github.com/repos/lionheart/openradar-mirror/issues/480/events","html_url":"https://github.com/lionheart/openradar-mirror/issues/480","id":98637723,"number":480,"title":"20315613: Xcode should ship a complete app as a template.","user":{"login":"openradar-mirror","id":13605213,"avatar_url":"https://avatars.githubusercontent.com/u/13605213?v=3","gravatar_id":"","url":"https://api.github.com/users/openradar-mirror","html_url":"https://github.com/openradar-mirror","followers_url":"https://api.github.com/users/openradar-mirror/followers","following_url":"https://api.github.com/users/openradar-mirror/following{/other_user}","gists_url":"https://api.github.com/users/openradar-mirror/gists{/gist_id}","starred_url":"https://api.github.com/users/openradar-mirror/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/openradar-mirror/subscriptions","organizations_url":"https://api.github.com/users/openradar-mirror/orgs","repos_url":"https://api.github.com/users/openradar-mirror/repos","events_url":"https://api.github.com/users/openradar-mirror/events{/privacy}","received_events_url":"https://api.github.com/users/openradar-mirror/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-08-02T21:06:26Z","updated_at":"2015-08-02T21:06:26Z","closed_at":null,"body":"#### Description\n\nSummary:\r\nXcode should ship a “complete” app as a template. It should include as many of the main platform app features as possible such as state saving and restoration, handoff, a Today and WatchKit extension, push notifications, auto layout, accessibility, storyboards, and probably 4 or 5 other major app technologies and aspects that I have forgotten about.\r\n\r\nI think it would be insanely useful for myself, others, and anyone just starting out to see how you guys imagine how a functional, robust, rich app that actually does something should be assembled and structured.\r\n\r\nDon’t gloss over error handling. Don’t skip major platform features like handoff or a WatchKit companion app just because it is “out of scope” or whatever. Don’t rush to put this together a few weeks before WWDC. We need a real, polished, functional, quality example.\r\n\r\nThe issue is, many of us out here no longer see how everything fits together anymore. WWDC session videos do not do a good job with this sort of thing. Neither does the documentation. Those contexts are always focused on a single framework or technology at a time. That’s great when you’re trying to understand those things, but how does it all fit together? Does it all mesh smoothly? I’ll be honest - lately, it feels like more and more of the APIs and frameworks do not meld together nicely and I can’t tell if it’s just me misunderstanding things, of if it’s really true.\r\n\r\nShow us how it *all* works together and we’ll make better apps for your platform. Give us a fully functional sample app with all the major parts and we can start there and *remove* the bits we don’t need rather than guess at the parts we’re supposed to add.\r\n\r\nThings are getting very complex and I have a feeling most of us are building houses of cards. Help us out.\r\n\r\nSteps to Reproduce:\r\n1. Try to make a robust, complete, rich iOS app using the platform's strengths.\r\n\r\n\r\nExpected Results:\r\nTo be able to make awesome things.\r\n\r\nActual Results:\r\nDrown in overwhelming complexity.\n\n-\nProduct Version: \nCreated: 2015-03-26 21:24:05.263610\nOriginated: 2015-03-26T00:00:00\nOpen Radar Link: http://www.openradar.me/20315613"}}