It’s not just the deployment, which I was able to figure out thanks to help from other users on this forum. It’s the fact that you can’t modify the urls or client paths or even see them easily once deployed. It’s the fact that the edge agent is unable to update itself, instead every time its updated I have to do a whole new deployment again, as if it wasn’t enough work the first time. Its the fact that nobody can do their own client updates anymore because they don’t understand that they need to go into the system tray, stop the edge agent, and then do the update. Seems simple. But you haven’t met my users. Even with screenshots, videos, and repeated reminders, its just not something most of them can do without asking for help. And forget about restarting the edge agent after all that. It’s the 30+ seconds it takes for the edge agent to launch a classic screen that would launch from the client in 5 seconds or less. All of that is to say, I don’t expect Epicor to fix any of those problems. I just want to get us to the browser and get rid of the edge agent once and for all, except for those people who really really need it to print.
Obviously when Classic is fully deprecated then there will be no launching the smart client… but what’s the point of mandating Browser First before that?
There was a comment about carrots and sticks… I just feel it’s in bad taste to attempt to push us towards the Browser faster by making the Classic experience worse (that’s what is really happening here, right??)… If Epicor wants me in the Browser then blow me away with how stable and not-buggy the screens and Application Studio are, don’t downgrade the Classic experience so that we go to the Browser because it’s the less miserable option…
Great question… one of the stumbling blocks to getting people to the new versions of the screens is that when running from the smart client, the new screens APPEAR to be slow, which then causes the new users of the new screens to say “I don’t like them, they are too slow”… the only way to get the truly enriched speed of the browser based apps is to actually run them from the browser. That is why we are pushing people to run from a browser.
Most companies have the vast majority of their customizations in about 10-20 screens… they might have another 10-20 that have a UD field here or there. in those cases, there should be no heavy lifting to get those into Kinetic. This leaves the balance of hundreds and hundreds of unmodified screens that can run in premium speed from a browser.
We resemble that remark with 22 screens that need to be rebuilt. We’ve been planning to try “Browser First” Jan 2025 and hoping the previously mentioned changes coming to the Edge Agent will made it easier to support and deploy.
Also don’t forget that classic Dashboards need to be uplifted too and in many cases --understandably-- it seems a rebuild is better then the conversion tools results. We have some heavy dashboards that will take to convert.
Why can’t we launch the browser from the client? That seems a lot easier to me…
I can appreciate that and will even take back my implication of nefarious motivations… I guess at the end of the day I just want to have control as an admin. There are some users / departments that will be 100% Browser soonish for us, some that will be 90% Classic for a while, and some that will be 80% Browser, 20% Classic for a while. Browser First could make sense for that later group, but kills us for the 90% Classic cohort and I guess is not relevant for the 100% Browser group (we wouldn’t even have smart client installed on the machines of those folks). I just want to have the capability in my hands of being able to implement the optimal setup for each group of folks, and I’m worried that Browser first takes that away from me.
Waiting for 2024. whatever to get to Cloud Pilot. Have PRB0276562 that cant deploy Edge Agent in RDS Environment. Will see…
Another Issue: When you load applications in Classic from Browser First any context menu items you added are missing.
I actually have the “Who moved my cheese” badge on this site, and I have to say:
I don’t miss classic.
Yes, I’ve been livid lately about server crashes since we moved to the browser, and the screen rendering issues.
But we upgraded to 2023.2 a month ago, and have not had a single crash (sure is a memory hog though). And the UI issues have not gone away, but they are pretty infrequent.
Re: Customizations - I despised customizations in classic. I did like 3 and gave up. However, it’s MUCH easier to customize in App Studio. I think I actually know what I am doing in App Studio.
Sounds like you need to have the badge revoked. 
I know it’s a change and we’re moving in the Kinetic direction just not as fast as we may need to.
Ha, I’m trying to remember how I got that badge. It doesn’t tell you like some of them do.
Still not a fan of the “new” MS Outlook. I want the old cheese back.
Ditto to TeamViewer.
Edit: found it; it was when they moved away from PDF user guides on EpicWeb. I still cry over that.
Books > Computers
Hey all,
This is great feedback and we appreciate it very much. As Tim said earlier we are going to take this topic offline from here and likely hold an empathy session (or more) to have more discussion vs. trying to resolve all your questions & concerns here. So, look for that soon and thanks again for the feedback - as always, we take this transition very seriously.
Our plans to migrate everyone to be fully browser based are intended to evolve fluidly as we see what works well and doesn’t as well as hearing reactions from all of you so this is all good and expected discussion in our view. Some of the changes may not also be clear enough without a deeper explanation than comes with an announcement. For example, login via browser only comes with many changes to edge agent to smooth out the experience, and has other behaviors so you can still launch a screen like classic mes, etc. I’ll pause there though on details and we look forward to continuing that discussion more in depth soon.
That’s because that one is specially granted by us Mods when someone is especially whiny about changes. It’s not automatic.
Hell, y’all could get some mileage out of that badge today
Brian & @timshuwy you guys are doing good work and thank you and everyone else on your teams for listening to our b**** fest today. (insert non-existing high-five emoji)
All good - This is how you solve hard product problems; you go find out, listen, adapt things, repeat. That’s what we’re all about and it works because people have valuable discussion fests, or whatever you’d like to call it 
Epicor has heard us, I’m closing this thread for now when @bconner / @timshuwy setup their whining session… It can’t be called that…(scrolls up) “Empathy Session” (i like my name better)
We will post and update.
our community is awesome and conversations like these are absolutely necessary. Don’t take me closing this thread as a negative I just want to make sure that we can all move on to a new more fun topic while Epicor figures out what to do next now that they’ve heard our feedback.
Thanks again