Notes

Rastin Mehr

Rastin Mehr's Notes

Rastin Mehr

Rastin Mehr

January 06 2017
Next #Anahita milestone is #MobileFirst
Unkown Person liked this
Nick Swinford
Nick Swinford
January 16 2017 Permalink
I'd really like to help with this as much as I can. I've read a good deal about React, but haven't experimented with it in any projects. I'm hoping my experience with Ember.js will help me pick it up quickly. No matter, I'm happy to help and want to step up my involvement in Anahita.
Rastin Mehr
Rastin Mehr
January 16 2017 Permalink
We've used ReactJS in our mobile apps. I've tried Ember.js, it is light and impressive. I'm still inclined towards React because there seems to be a lot of activities in their community.
Nick Swinford
Nick Swinford
January 16 2017 Permalink
I know, I was just saying that I'd hope my experience with Ember.js would help me get up to speed quickly with React.

Let me know how I can start helping out with the switch over.
2 people liked this
Rastin Mehr
Rastin Mehr
January 17 2017 Permalink
Your knowledge will be invaluable. I'm doing research right now on what each technology provides, their ecosystem, and how they can be part of Anahita's architecture. Then I'm going to write a few paragraphs to outline what needs to be done in 4.4. Then we can start prototyping and gradually build forward.
Scott Crawford
Scott Crawford
January 26 2017 Permalink
How extensive are the anticipated changes required to implement MobileFirst? Would this entail a bottoms-up restructuring of all views and related media?
Rastin Mehr
Rastin Mehr
January 26 2017 Permalink
Quite extensive. All the UI elements - except the publicly visible ones - will be rendered using Javascript. The idea is to use the php components as APIs as much as possible and let the client side render the user interface elements. Still unsure about the details of it, but that's what we're aspiring to achieve.
Rastin Mehr
Rastin Mehr
January 26 2017 Permalink
It's more than just MobileFirst. We want Anahita to become a progressive web app. Right now we are partially there, but JQuery isn't the best technology for that purpose. Right now we are providing the user interface baseline and then progressively load additional snips of html code to add more to the page. Ideally we would want to only load data and do all the html rendering in the browser.
Rastin Mehr
Rastin Mehr
January 26 2017 Permalink
I'll publish an article in the project group which outlines the 4.4 goals
Scott Crawford
Scott Crawford
January 26 2017 Permalink
That would be very much appreciated - perhaps touch on some high-level terminology as well if you could and how it relates, eg progressive... things seem to have evolved a bit since mobile first had once meant responsive, at least as I had understood them at the time. And perhaps related, I've noticed google starting to cache some pages under technology termed AMP I believe, intended to facilitate mobile consumption relative to bandwidth and some other factors.

Part of the motivation in asking was also that I have been looking into 2017 priorities for new custom Anahita apps, one being more content-oriented and the later being more-presentation oriented. I think your comments here are enough alone to put one above the other for now, but the additional insight could certainly help drive the planning on the later, or even both.
Rastin Mehr liked this
James Imani
James Imani
January 27 2017 Permalink
@Rastin...I am really curious, how your final solution will look like in the end. Hopefully easy and flexible to use.

Personally, I like the approach to have Anahita's php-core-system as a backend system, just responsible to retrieve or deliver data that the frontend-framework is easily asking for per JS.

Now, what we need is a JS-framework, which includes a client-side HTML-rendering library? Means, it should translate JS into HTML5?
Rastin Mehr liked this
Rastin Mehr
Rastin Mehr
January 27 2017 Permalink
@imani you got that right, most of the HTML will be rendered by JS.

Powered by Anahita