Moovweb XDN vs. Swiftify

Depending on a site's structure, and a team's business flow, Moovweb could be a great fit for a business looking to optimize its desktop site for mobile and tablet devices. Given that more and more businesses are designing for "Mobile First" or at least making pages tap-friendly for tablet devices, there are cases where some businesses will find responsive or simplified designs as a good enough solution. However, for a large portion of sites, a unique experience is needed for mobile and a different experience is needed for tablet. Customer moments are different, and a single site that simply "fits" onto a smaller screen really doesn't address the change in the customer moment. Moovweb is able to transform the desktop site into optimized sites that streamline the experience into what is most impactful to the customer in that moment, based on business logic and with minimal support. After considering a responsive site, the Moovweb solution was the right choice for our business and for our customers, and the results are proving we made the right choice.

For me as a picky person I never used the file convertor but for a small portion of code, it is good. With the classes that have more than one initializer, it got confusing and I had to dig to find the exact issue to fix.

Incentivized

• 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

• Put in your Objective-C code, select the version of Swift language to convert, click convert. That's all!
• Swiftify is now creating a platform to convert Objective C to #C, something that can help for different development projects platforms.
• Swiftify offers a few free converts to try to show you the power of it. Their price for a subscription plan is really good for big projects.

• 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.

• It lacks general performance and availability
• It doesn't handle Objective-C macro well
• Overall conversion speed expected to be much better

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

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.

There are constant upgrades to improve the conversion.

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

Swiftify tries to convert the code even if the code can not be executed in a real situation. I chose Swiftify because most of the times you just need to convert one line, one method... That of course, it is using and used by other code that you didn't add in the conversion code, but you just need to convert that for now. In this situation, Swiftify converts the code, other ones such as iSwift will report an error in the code and will not convert it.

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.

• good ROI, saves a lot of time.

Incentivized