# RealWorld example app architected with the Effect pattern

**URL:** <https://discourse.elm-lang.org/t/realworld-example-app-architected-with-the-effect-pattern/5753>\
**Category:** Show and Tell\
**Created:** [May 10, 2020, 12:40pm UTC](https://discourse.elm-lang.org/t/realworld-example-app-architected-with-the-effect-pattern/5753 "2020-05-10T12:40:33Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![gampleman](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/gampleman/32/43_2.png) [@gampleman](https://discourse.elm-lang.org/u/gampleman)\
**Post date:** [May 12, 2020, 9:31am UTC](https://discourse.elm-lang.org/t/realworld-example-app-architected-with-the-effect-pattern/5753/9 "2020-05-12T09:31:00Z")

</div>

One issue I had with elm-spa architecture was going from one Page to another with information that couldn’t be encoded in the URL. I think part of that problem was the directionality of that information, where one goes from URL to message to state. I was wondering if this pattern could reverse the direction and go from message to state to url.

What I mean by reducing complexity is that personally I always find the `onUrlRequest` and `onUrlChange` options in `Browser.application` pretty confusing. Thankfully it’s the sort of thing one usually sets up at the beginning and then doesn’t mess with much, but I feel that the routing APIs could use a bit of streamlining.

---

_[View the full topic](https://discourse.elm-lang.org/t/realworld-example-app-architected-with-the-effect-pattern/5753)._