[jed_watson]

The app framework is structured as a React mixin, everything else (lists, form controls, etc) is just React Components you can drop into your app. So for the most part how you structure your app is up to you (except for the scaffolding necessary for the view transitions). It's inspired by react-router (after the recent changes) in terms of getting out of your way.

Other than that, aside from needing some sort of compilation step for the JSX (our demo project uses browserify and gulp) the rest is up to you.

I haven't used Om or Reagent yet but I don't think there'd be anything preventing them from working with Touchstone.

[colinramsay]

Is there any reason not to just use react-router?

Edit: ok I found the createApp mixin and I can see you're doing a lot of stuff in there to support the touchstone app... It would be sweet if you could delegate some of that heavy lifting and integrate with react-router at the same time...

[jed_watson]

You need a lot more control over how the views transition, pass state, etc. in order to create a native-feeling app.

The paradigm of links and parameters falls short, and eventually TouchstoneJS will exert a lot more control over the transitions. Right now we're using CSSTransitionGroup, but I expect we'll move to a JS-based transition method (possibly with tween-state) so you can do controlled or partial transitions (required for things like drawers or swipe-from-left to go back)

We have spent a lot of time looking at react-router though, and are using it on other projects, and are / will be borrowing quite a few things :)

[colinramsay]

That's fair enough. I'm looking forward to testing Touchstone out soon, I've got a test project in mind!