Great, but could be improved.
-
Edit: Improving my rating due to recently improved support and not wanting to hurt a company’s work due to the one bad egg I appear to have dealt with. Technical feature requests remain.
Initially, Arlo seemed promising, however mid-way through development issues with syncing of events started. The Arlo support team took up to 48 hours to return support tickets and essentially blamed me for the issue. The workaround was to launch the site to a staging server, sync Arlo and then copy the database back to local (a solution that I had to formulate).
Development of a custom theme was not as “clean” as described as even the “Custom” Arlo theme (which is aimed at developers who want to write their own CSS) injects javascript for popups and stylesheets which complicates development isn’t mobile-friendly and results in more server calls than necessary.
The controls for displaying events are also in need of improvement, as depending on where you require them to be placed on the template the hard-coded heading structures will result in the incorrect page heading structure.
The integration is also not as seamless as described, the checkout page will redirect the user to Arlo’s own checkout site which could be improved in terms of design. All you can do is change the logo.
The choice to use Arlo was a decision made by my client prior to my development. Regardless my intention and efforts centred around integrating Arlo to the best of my ability.
- The topic ‘Great, but could be improved.’ is closed to new replies.
