This is still a hilarious thread. Glad we’re upgrading to classic E11 first, before setting off the k-bomb, as it were.
Kim
It wasn’t bug free, but it was intuitive for programmers because it worked pretty much like every other IDE out there… And while there were bugs, there were also workarounds for most of them.
Ah. It’s becoming clear now, why so many here miss it.
I hated classic customizations too. But just because I complained about classic doesn’t mean I can’t complain about app studio too. Its not a zero sum game and I have an infinite ability to complain about buggy software 
3 Likes
Not when Vantage 8.0 came out. People wanted their VB.Net screens back. Form binding was quite different than every other IDE. csm.GetNativeReference wasn’t used in WinForms or Access or anything else…
After 2023.1, I’d say we’re about here.
Seriously, if I could take us back in a Time Machine to tell those folks in 2006 how great the .NET client is…
4 Likes
I’d agree, I just hope that this time around we start off posting and distributing all Kinetic advancements so that everyone has the chance to learn it instead of recommending professional services for everything that can’t be explained via documentation. Empower the user base. Share examples of customizations.
4 Likes
When I’m working on implementations, I always use the same line. “You’re going to hear that your old software is the worst thing around, until the day you go live with xxxxx. On that day, your old software did everything great.”
3 Likes
Your chart is pretty typical however it completely ignores the biggest gripes, which I would hope in most major platform changes isn’t common.
A fully functioning product is typically available before cutover\release.
Hopefully the product has clear and adequate documentation (that matches the product).
Typically, you get many additional features, not lose them (without suitable replacement).
We are learning a product that is still in development and (very) subject to (huge) change.
I’m not here to bash for the sake of bashing, I am voicing my concern as a customer\end user. Anybody who does consulting I am sure will make this work, unfortunately there’s going to be a huge swath of people who dont and are going to be stuck relying on $$$/hour.
2 Likes
Yes! Epicor needs to be doing this. Right now @hmwillett has 10x the solid content here, compared to what Epicor has put out over the last 2 years.
Sure, and the early adopters will be paying the consultants to learn how to do this on their dime. Right now, you either put in the time doing trial and error to figure out work arounds for all the quirks, or wait for better documentation so you can follow steps and get the customization completed efficiently.
1 Like
Dude I am glad I am not the only one thinking it.
2 Likes
Maybe in 2003. Gmail was in beta from 2004 to 2009. Software publishing has been going the minimum viable product route for at least ten years now.
For V8, there was no easing over. You got the new client in all its flakiness. Yes, I agree it’s painful. But frankly, it’s an easier path than the launch of V8.
I know we want to wait until it’s perfect but the truth is that users don’t know what they want until they see it. Even then, they may not realize that they want a car and not a faster horse. This is why we do this dance. What can I say? Invent a better way. Zuckerberg and Musk will be your pool boys. 
2 Likes
And then share what you can with the public in the spare time that you have. Which by the time you get done figuring out whatever it was you were studying you’re exhausted and it’s mind boggling to try and put into a concise epiusers post.
2 Likes
@Mark_Wonsil Amen to all of that. There is no user testing like forced user testing.
My only Monday-morning QB advice would be the pity I have for the SaaS people who were forced to abandon classic way too early. [See redaction further down]
I don’t mind defaulting people to Kinetic and waiting for the complaints, and then saying, “Oh - did I not tell you that there’s a way to still use classic?”
I mean, the new version of Outlook is still allowing me to stick with the old version until 2024. A rolling beta is fair.
No one has been forced (by Epicor I mean), that’s a company decision.
I use classic for 95% of what I do.
The rest of my company is about 80-20.
1 Like
I am trying to use Kientic as much as I can and yeah, our users use Kinetic until there’s a really big issue with it.
1 Like
It is… when that’s what they tell you up front.
The message that was being put out for a while was, “Kinetic is Production Ready”…
2 Likes
When’s this thread gonna lock?
The only plausible and foreseeable resolution to this thread.
1 Like
Hahaha Chris
SafeForWork?
Like dis?