Moovweb XDN vs. React

It depends on who you are. If you are very small it won't be worth the money. If you have a very cranky site with nested tables coming out of every orifice, maybe you should look at a replatform or desktop rewrite first. If you have a site with vast numbers of custom content pages, it will work but may not be cost effective. Moovweb is well suited to you if you need the ability to control mobile experiences and respond to changes in mobile and the demands of mobile aware executives who want to move more quickly than your current IT processes allow. It is well suited if you need something quickly but also want the option to bring mobile development and support in-house some time in the next year or two (which you should). It is well suited if your desire to improve a responsive experience has been thwarted by internal fears over the impact that it might have on desktop. It is well suited if you want to experiment on mobile but do more than just change the color of a button or make a font larger. It's very good at letting a UX team try things out and see what real customers do.

React is a JavaScript user interface construction library that works well for:

• Developing web apps with dynamic and complicated user interfaces.
• creating reusable UI elements that may be used in other applications.
• creating single-page applications with dynamic content updates that don't require a page reload.
• The Virtual DOM's effective updating mechanism allows it to handle large volumes of data updates.

React, on the other hand, might be less suitable for:

• Websites that are simple, stagnant, and have no interaction. Other libraries or simple HTML, CSS, and JavaScript may be a better fit in such circumstances.
• Web sockets may be a better choice for applications that need real-time updates, such as chat or gaming apps.
• When creating mobile apps, React Native is a better option.
• Server side rendering only, as React is designed to run on the client side.

• Moovweb takes the time to really understand your needs and challenges and is willing to work with and address them. They are partners during and AFTER implementation.
• Moovweb and their implementation partner 64Labs has a fantastic response time and work ethic. They really will do what it takes.
• Moovweb takes the time to share their product road map with customers.

Incentivized

• React is fantastic for building performant user interfaces. Our web app is snappy and great for our customers.
• React has the philosophy of doing one thing and doing it well which is the view layer of the application. This makes it incredibly intuitive and flexible for developers to use.
• React has lead the way in being able to write modular and structured code. It is a drastic improvement since the days of spaghetti jQuery code.
• React has an unmatched community. The amount of tools and libraries available is fantastic, and there plenty of solutions available online for common problems.

Incentivized

• Depending on how your site is built and maintained, there may be a different solution that will be a better option for your business and customer needs.
• At the end of the day, this is another layer that is added to your development plan and time to ensure updates work across multiple devices. Moovweb is really good about the turn-time for these updates, but there still needs to be the added QA step for M&T optimization per release.

• Debugging React is challenging. Bugs in react code generate stack traces internal to React and it is often totally unclear how it relates to the code you actually wrote.
• Relating your React elements to corresponding DOM elements is difficult. The intentional separation of virtual and actual DOM also makes it difficult to map the elements to the structures in the DOM. This is partially ameliorated by the use of the React dev tool, which provides a DOM-like view of the React elements, but the tool still does not provide a direct correspondence with the DOM that is often necessary to figure out why something isn't right.
• Because JSX is React-specific and not a language feature, a special compilation process is necessary to convert JSX code to normal JS. Coming from a C++ background, compiling things doesn't bother me, but many JS developers are used to a less structured development.

Incentivized

Personally as a Mobile Architect I am a huge proponent of building mobile-first responsive websites. I will always fight for a lobby for businesses to build sites with all devices in mind and not focus their attention on desktop driven sites which are then adaptively scaled to meet the demands of the business, in my opinion leading to a never ending cycle of building separate media queries to compensate for every device the business chooses to market to

Incentivized

React is just a bit of a different animal. I was avoiding it for the longest time. I thought for sure I would land on Vue or something else with a more approachable and familiar appearance. But after taking an online course in React, I started realize what people were raving about (and complaining about) and decided to implement it at our office for one of our products.

Incentivized

Good set of customer success people combined with the flexibility to use high-quality onshore partners if workload increases at busy times. I think Moovweb's support efforts are pretty solid.

Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.

Incentivized

1. Don't spend weeks in design. Because of the way the technology works nuances of design can change very quickly further down the line. We have changed the look of the product list for a client a week before launch.
2. Push for getting the project into UAT within four weeks of the kickoff of the project. There are few retailer projects that need to take more than that. In my experience the more concentrated the timeline the more effective the implementation.
3. Check that there are no major changes planned on desktop during the time of your implementation (another reason to keep the development to four weeks).
4. If you have custom mobile content requirements, get them to your implementer at the start. Moovweb is great at heavy-lifting existing content, but your implementer will need to recommend solutions for custom content that will need to be tested. Get these requirements out at the start.
5. Make a list of your desktop plugins. Moovweb can handle them all, but they can be handled in different ways
6. If you have Paypal/Google Wallet and want it on mobile as part of your project, talk about that early on.

This is the only mobile technology we have used. We went through an extensive research and vetting process. In the end Moovweb was the best choice for technology and business needs. We considered the following companies: Moovweb,Mobify, Usablenet, Mad Mobile, SKAVA, Wompmobile. Forrester has a mobile infrastrucutre services report that could be very helpful.

Incentivized

While this is a widely contested debate with various blog posts and benchmarks all over the place, its really a personal choice to determine what works for the team. Coming from a Angular 1.x background, I decided to try a new framework when Angular 2.x was announced and at that time React is gaining popularity and Vue hasn't taken off yet. Compared to Angular 1.x and Vue (hybrid of React and Angular) that split the logic from the html templates, I loved the way React breaks code into components using the jsx syntax. In my mind, this allows for cleaner components and easier maintenance

Incentivized

• The implementation was 4 months from start to finish. Mobile is about 10% of our visits today and our mobile revenue for the first half is about $200K so we will have a payback in 1 -2 years.
• Moovweb is not the most economical solution out there. It is one of the most comprehensive for sites needing all their content available for mobile.

• Our web applications now run much faster because the whole page doesn't reload
• We spend less time developing UI components because a lot of them are readily available on NPM
• We don't have to optimize apps for multiple browsers since React natively supports it.

Incentivized