What's folks latest take on Mantra approach: isomorphic modules & native apps?

[adamginsburg]

Hi I noticed a few threads that have not been updated for several months

Say No to Universal Apps

Absolutely agree, but the title threw me because when I think “isomorphic” I think same code between client and server (AKA “universal” https://medium.com/@mjackson/universal-javascript-4761051b7ae9#.ex2okb6lc), not same code across multiple clients. Regardless,

https://voice.kadira.io/say-no-to-isomorphic-apps-b7b7c419c634#.a69y7lszd
and

Say Yes To Universal Apps

This is something I constantly go around in circles with: Scenario: A clinician comes up with an awesome app idea, and tries their hand at some design work. They create some wireframes and maybe some photoshopped layouts using their component library of choice (Bootstrap/Polymer/Material/etc). They then hand off the wireframes to a staff member who is new to Meteor but enthusiastic about the problem domain. The clinician and staff member start their design with a desktop app because that’s…

Any thoughts/recommendations on a good architecture, pls?

background: We have been building an isomorphic app for some time now, and looking to improve the user experience by caching/making things more “native-like” than a Cordova app.

[prime]

This is overview of Mantra:

Mantra is an application architecture for Meteor. With Mantra, we try to achieve two main goals.

High Maintainability

Maintainability is a key factor for success when working with a large team. We achieve this by unit testing every part of our app, while following standards for everything. Then it’s easy to on-board new users and work with teams.

Future Proof

JavaScript is a land of choices. We have more than one best thing for each problem. It can be hard to tell what’s the best solution now and what will change in the future.

Mantra relies on a set of core principles that will last for a long time. Then, we let others change as needed.

Looks promising!

kadirahq/mantra

[adamginsburg]

@prime

JavaScript is a land of choices. We have more than one best thing for each problem. It can be hard to tell what’s the best solution now and what will change in the future.

Thanks. yep, saw that… .just thought I’d check if there was current momentum around this approach or some other approach/architecture that was more current/has more momentum?