Until the smart people get here, I’ll see what I can do…
I’m doing the same thing as you are, jQuery Mobile front-ends in addition to a full web version for many applications. There are a couple of ways to handle it, below are some thoughts about the options I’ve considered.
The best method is going to depend on how you structure the application and what kind of data you want to return.
Maybe you want to create a responsive interface by pre-loading the entire client-side / UI by putting it all into one HTML file containing the interface elements. It would load external data via AJAX (JSON or HTML fragments) and even possibly store that data in local storage for caching, offline usage, or other purposes.
Maybe you would rather have individual HTML pages loaded with the jQuery Mobile transitions as they are clicked on instead of having a responsive, pre-loaded UI built in to the client.
Depending on what you do, you could create a separate endpoint route for mobile requests (such as http://www.foo.com/mobile/handler/action) that would always return JSON or a code fragment (you could use an interceptor to further decorate the response), since the mobile application / site would always be making the requests to that endpoint.
Or, you could do an Event.isProxyRequest() in your existing handlers to determine if the request is coming through the ColdBox Proxy, and then return JSON or your code fragment that way. This would allow the handlers to run normally in web requests, but return data to mobile data requests made through the proxy. Then just make calls to your proxy (or even directly to the handlers) from the mobile app. For prettiness, you could make a rewrite rule for http://www.foo.com/mobile to point to your ColdboxProxy.cfc and make the request to the pretty URL from your mobile app, which would send the request through the proxy to your normal handlers, which would see the proxy and return JSON or fragment, as you desire.
If you just wanted page-to-page transitions, then you’d simply make a default layout to load for the mobile site, then load views containing the data using the jQuery Mobile page / load functionality.
You could create a mobile handler, specifically to handle requests, but it’s really not needed if you implement some of what’s already there for you in ColdBox.
Hope this helps, feel free to hit me up about any questions.