Editor SO SLOW ! Awful Developer Experience

Developer corner
1

Am i the only one experiencing a very slow editor ?

To the point that it gets painful to work with weweb

it is happening, when

  • loading the editor
  • loading a custom coaded component
  • obvisouly typing to find a variable has always been very slow.

Would be good to have a focus from the WeWeb team on those little DX things, because that’s getting very painful to continue building with weweb those days

2

Hi @Matt :waving_hand:

Can you define “very slow”?

I’ve just tried on 10 projects. Most took 3-5 seconds to open. A couple took between 10-20 seconds to open but, once inside the project, the switch between pages was quick.

3

very slow, means several minutes almost each time

4

Ok, definitely an issue then. Have you created a bug ticket with a video and info to reproduce?

5

https://support.weweb.io/ does not allow me to select another workspace.

how am i supposed to report the bug ?

6

Hey Matthieu,

First of all, the support app should allow you to select any workspace you’re a member of. If you’re not a member of the workspace where the project presents an issue, you have a few options:

  1. ask the workspace owner to invite you, then report the bug
  2. ask the workspace owner to report the bug themselves
  3. report the bug from your own workspace and specify in the report that it concerns another project, making sure you link to that project.

Does that help?

PS: if you are a member of the workspace and the support app doesn’t allow you to select that workspace, please send me a link to the workspace in a direct message so that I can investigate

7

Nah - you’re not the only one, but they don’t seem to care. Everytime I pull up a larger WeWeb project - which now happens every few months and thankfully not daily, it loads for like half a minute. It’s not a bad experience, it’s a non existent developer experience.

8

That’s simply not true. As far as I’m aware, all the performance-related tickets where the user has answered our follow up questions or agreed to jump on a call with us to help us debug the issue have been solved.

If you have an open performance-related ticket where that was not the case, please share it with me. I will personally follow up with the team.

9

okay, so yeah, that’s, not an isolated problem.

I started to think I was the only one complaining.

10

Nah, I even know whole agencies stopping using WeWeb just because of their inability to address performance issues. But it was more of a memory leaks issue, which i hope they solved (though I wouldn’t be surprised if not).

11

+1 for performance issues

12

Can you send me the link to the support ticket you created so that I can personally follow up with the team?

13

+1 The editor exhibits a markedly sluggish loading speed upon opening.

Yesterday was all fine…

14

I’m not surprised they’re moving away.
And a lot of end-user companies are also currently moving away.

  • a slow editor that gets working with weweb harder and harder as the app grows
  • for me, the AI displays “The current context is too large for the AI to process. Please reduce the context size and try again.”
  • Nothing has been done to work in collaboration on an app,

And all of this above gets solved when moving to code.

Obviously, you don’t get those problems when your app is a blank canvas, but then after the app has grown, it gets very complex to continue working in WeWeb.

So clearly a bit disappointed that those issues are not a top priority to solve first

15

The issue has been resolved; it was not due to WeWeb, but rather to a custom component.