- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
- We had Classic turned off for our instance; we're 100% NWE. No change.
- We're only 2 years in, 200 active users, 1200 or so total users, so not a big deployment by WF standards nor much time to clutter or over-complicate, or have any real legacy baggage.
- WF claims to be enterprise-class and scalable, so speed should never be an issue.
- This isn't a matter of hating on the new app and emotional attachment to the legacy one. Classic is in many, many ways just more efficient due to better performance and tighter UI. Way better performance.
- WF has clearly told us, and since we didn't have a choice, we jumped into NWE ahead of time so we could start complaining. Unlike Narayan, I don't have the option to threaten to leave WF…or honestly some days I would.
- WF has so many other "WTH?" issues we seriously considered bailing before launch. If this speed issue was in-place at that time, that might have tipped us over the edge. Some of the things I've had to add Idea Exchange's for baffle me; and this speed thing is equally aggravating.
Views
Replies
0 Likes
Total Likes