Hey! I would consider fx/create-app bad, yes. Maybe it should be deprecated. Maybe it should get an option to not use wrap-async. In my own experience using cljfx I stopped using even more stuff — I'm not using effects/co-effects, and I'm not using contexts.

So maybe the closest to what I found useful is an example in https://github.com/cljfx/cljfx#map-events

With the exception that the example uses atom mutation in map event handler, while I made my event handlers return a function that is then used to swap the state.

I updated https://github.com/cljfx/cljfx/blob/master/examples/e09_todo_app.clj to show how I do that in Reveal (with the difference that in Reveal map-event-handler is a multi-method)

I received very vocal reports of happy users of ctx stuff that I don't use, so I'm not sure what's the "one-size-fits-most" would be. e09 is my opinion though 🙂

Interesting. I'd say an alternative to fx/create-app without wrap-async would be good. I like the idea of the "full enchilada" pure app on the surface at least, so I'm just cranking out this boilerplate for my case, which seems to cover it:

(def renderer
  (fx/create-renderer
    :middleware (comp
                  fx/wrap-context-desc
                  (fx/wrap-map-desc (fn [_] {:fx/type root})))
    :opts {:fx.opt/map-event-handler
                                   (-> handle-event
                                       (fx/wrap-co-effects {:fx/context (fx/make-deref-co-effect *context)})
                                       (fx/wrap-effects {:context  (fx/make-reset-effect *context)
                                                         :dispatch fx/dispatch-effect
                                                         :read-dir read-dir}))
           :fx.opt/type->lifecycle #(or (fx/keyword->lifecycle %)
                                        (fx/fn->lifecycle-with-context %))}))