To elaborate on this a bit, I originally wrote ABRouter for an iOS app I was building that talked to a RESTful web service. The app would register the relevant URL patterns, and the web service would hand back paths for each downloaded or navigable resource. When the user taps on a UI element that will show a new screen, the app tells the router to load the corresponding path. The router builds a new view controller that corresponds to that path, and the VC then gets pushed onto the navigation stack.
What's great about this is that deep linking and loading UI from push notifications becomes a trivial task, and your UI flows are no longer hard coded.
1 comment
[ 3.4 ms ] story [ 10.2 ms ] threadTo elaborate on this a bit, I originally wrote ABRouter for an iOS app I was building that talked to a RESTful web service. The app would register the relevant URL patterns, and the web service would hand back paths for each downloaded or navigable resource. When the user taps on a UI element that will show a new screen, the app tells the router to load the corresponding path. The router builds a new view controller that corresponds to that path, and the VC then gets pushed onto the navigation stack.
What's great about this is that deep linking and loading UI from push notifications becomes a trivial task, and your UI flows are no longer hard coded.