> On Apr 15, 2016, at 4:43 AM, Sebastian Kaspari wrote:
…
> Regarding libraries that introduce new patterns: I'm reserved - They make
> life simpler at times but they come with a cost: You need to learn how to use
> them. New volunteers might not be able to contribute without learning the
>
I want to throw in another video from last year's Android Dev Summit in
Mountain View:
Android Application Architecture
https://www.youtube.com/watch?v=BlkJzgjzL0c
I've been looking at MVVM too but I haven't fully used it in an Android app
to have an opinion.
Regarding libraries that introduce n
>
>
>- Isolate state.
>- Pursue immutability and idempotency.
>- Separate state changes from presentation changes.
>- Don't be afraid of transforming state into the minimal
>representation necessary for display.
>
>
Just wanted to briefly chime in and mention a great architectur
Emily has recently been exploring state-driven frontend design on iOS for
her menu work; I'd like to see her chime in here with her experiences.
My 2¢:
> I've noticed that these patterns are not something that we've been
> explicitly doing on this team but could potentially benefit from – does
>
Michael Comella wrote on 11.04.2016 22:44:
Experience with these architectures on other platforms (e.g. MVC in
web dev) would also be useful to hear! :)
I've been using strict MVC in XUL extensions and web apps. The way I use
it is:
* Model
contains the logic, that is all abstract functi
Hey front-end Android devs.
I've recently been looking into different architecture techniques for
Android applications – e.g. model-view-presenter. I found an article [1]
that gives an overview of what has been popular on Android:
http://zserge.com/blog/android-mvp-mvvm-redux-history.html
I've
6 matches
Mail list logo
