Itās been the biggest pain point for our power users from fully adopting Kinetic in the browser: the usability of the Method/ Data Directive and BAQ designer screens ā these windows use up so much screen real estate, and everything requires so many extra clicks 
Thereās a lot right about the Kinetic UI/UX, but BAQ and directive design isnāt one of them lol (and report style uploading, yikes 
)
Iāve ben browser-only since I started in Epicor a year and a half ago (except occasional forays into E10.2 for maintenance) ā¦
Is it really that bad? What is wrong with the designers that E10 did so much better?
one wordā¦ DENSITY
All I can think of.
For me, mostly screen elements taking up a lot of real estate that cannot be hidden or minimized, and it is a stupid excessive amount of additional required clicking to do the same breadth of work. Error reporting not returning the same level of detail, general workflow while interacting with the different elements
I wouldnāt have to work anymore if I could get paid in Kinetic clicks/hr
I assure you, I have done some really dumb things with codeā¦
Atrocious
Absolutely. @JasonMcD would likely make an excellent code monkey. He has the mind for it.
Love ya either way Mr. Widgeteer.
Surely you are not suggesting that we stop all progress. We have introduced many new things over the past few yearsā¦ lots of āEpicor Ideasā that all of you have suggested. They have been very well received. We introduced faster MRP, better Buyer workbench, the NEW Explorer window for Quote to Cash and Procure to Payā¦ New features and functionalities all around.
No we are suggesting be mindful that progress for the sake of progress isnāt always a good thing. You made a ton of āprogressā but lost a lot along the way, and we really need Epicor to finish up the progress they already started before they start new āProgressā.
When we put in a ticket with the literal code that needs to be inserted to fix the issue, it shouldnāt take months to get said code into the product. We already did the hard work for you. I understand not having everyone doing the same thing, but there are a LOT of low level bugs still sitting out there that cause us a lot of pain that new wizbang UIās arenāt going to fix. This is software for running a business, style over substance is really not helpful.
Progress would be stabilizing on the changes that have already been introduced, e.g. 2025.2 - The Boring Edition with no new features but bug fixes
I had questioned the resources spent on the Explorer view two years ago when Kinetic was a mess (and still is).
I donāt think you are understanding what we as users are going through trying to implement and run businesses through kinetic.
When ideas are created by Epicor employees, such as what started this, it feels like our concerns are not being heard and instead new features are created, even ones that didnāt satisfy what everyone requested. Example below
Epicor is a great product and we all wouldnāt be here otherwise, but the pitchforks came out and this thread turned into a dumpster fire for good reason.
Absolutely not, but I would be much happier if those items were way lower on the priority list.
Whether Epicor would like to admit it or not, they are not in the end stages of a platform change, they are still firmly in the middle.
Lots of functional issues, inconsistencies, breaking changes from version to version.
There is still a large gap in parity between classic and the new UX.
Am I suggesting yāall stop innovating, or pushing forward? Not at all.
I am suggesting that a little soul searching is needed and to realize that this is a product your customers use to run our businesses.
Focus more on stability, and introduce new things when they make sense, and when we can fully, and hopefully happily make use of them.
All right itās a new Friday. Letās move it along to a new set of ideas.
Weāve made our point ā¦ over and over and over again