Front End Developer's Perspective
June 26, 2019
Front End Developer's Perspective
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Optimizely
It is being used by a small team within a department primarily for A/B testing. For example, to promote user registration, we might want to test out a new feature which could be anything from a new design for the registration section or a mini-standalone application. Before rolling it out en masse, we would test this out in a limited scope to compare relative registration levels.
- Can target a feature to a specific audience like desktop Chrome users only.
- Can do multiple layers of A/B testing.
- Can roll out a new design test in a matter of hours.
- The webapp itself is sometimes slow to load.
- The code change difference is one giant string, would be easier if formatted for readability.
- Definitely money saved from not doing a full-on implementation on some feature that turns out is not an improvement.
- Turnaround development time is quicker too than if we were to roll it out.
As a developer, I just implement what I'm told. I can't speak specifically to how it works from a stats perspective but certainly, the manager who runs these experiments sees a lot of value in executing them. By doing it all on one platform, we are able to turn around quickly and make decisions moving forward quicker.
In some ways, when we did a demo with other products, some things were built in like scroll tracking. But in many ways, Optimizely just was easier to use.