WeWeb - update on what we are working on at the moment

could you maybe give a sneak peak for the GANTT? I need to determine if it’s worth the wait or if I should go for a webcomponent now.
I have a rather complex plan of using the GANTT as an interactive tool to build tourplans. Are you implementing something rather simple or will it be a highly customizable solution? I’d need more like a flexible scheduler than a typical GANTT

1 Like

Hi,
thats on me, on my research I was redirecting to an opened bug on Ag-grid about it, but we recently upgrade the version and it should work now. Will be fixed on the next release with the onClick behavior :slight_smile:

3 Likes

Thanks for the heads-up. I just edited the initial message and added the following: “Branching: the product team has completed the first version of the qualification, and it is now with the developers for review. We’ll share an initial estimate of the time required to build this feature in the next bi-weekly update.”

Once we understand how long development will take, we’ll share an estimated timeline for delivery.

5 Likes

yes, @aurelie is on it, it will be released probably next week.

@Alexis would you mind recording a quick video for Andreas to show him our progress?

That would be great I’m basically deciding between day pilot and the integrated component at this point.

Hey @Raphael
any update on this one?

We have one project where the decision about Xano vs Supabase heavily depends on this feature.
Just want to know if it’s realistic to expect the feature to be available in next 2 months.

1 Like

Any news on the long awaited SSR front ?
i feel like a few of us would really benefit this update cc. @what.gift @Matthew @vfede

2 Likes

Same here, very much hoping for SSR to be a real priority :folded_hands:

3 Likes

So desperetly need it. Here’s my real live use case I can share for context:

This product is showing as £37.94 on Google (auto set by Google), yet this chocolate cake is actually listed at £50 on my Weweb built site.

As we can’t set dynamic schema, attributes, metadata, etc, it’s not possible to control these values. It’s also random luck this page is indexed as most aren’t due to canonical URL issues.

I’ve got 4000 products like this and counting. As I’m 1.5 years into development, I’m beholden to WeWeb!

If anyone has found workarounds, I’d love to hear it.

3 Likes

@Raphael will there still be a bi-weekly update? I didn’t see a post last Friday (no pressure, I’m just very curious what’s the latest news and developments! :slightly_smiling_face:)

1 Like

Was also looking for this, I’m really keen to see the where the new modal/dialog system is at. As the current version as a component is extremely annoying to work with.

1 Like

Finally, i’m not the only one concerned with Weweb SEO issues. Since the end of prerendering end of 2024, my trafic dropped 75%, and new pages are not indexed anymore.

4 Likes

You’re definitely not alone. SEO is not getting the attention it deserves. However, I’m not familiar with the prerendering issue? Care to explain more?

Hi everyone! Here is the latest roadmap update, apologies for the extra week I took before updating you all:

  1. Improving the quality of the AI-generated UI & logic: this will go live tomorrow or Thursday! The AI generation has improved by an order of magnitude on the front-end, the UI generation is much better, and logic handling is significantly more reliable (it finally works!). We haven’t yet focused on enhancing the AI’s integration with Supabase, that’s planned for a later phase. Our next priority is getting the AI to work with the design system, so it can produce consistent designs across pages. This will require 3-4 weeks of work. During that time, we’ll also collect your feedback to further improve and stabilize the new AI generation.

  2. Datagrid improvements:

  1. Here is the progress on our long list of components:
  • Gantt - in QA
  • Chat - in QA
  • AI chat - in QA
  • Currency input - in QA
  • OTP Input - in QA
  • Stepper - in QA
    All of the above should go live between this week and the second week of June.
  1. We are also working on the following improvements for our existing elements:
  • Add a focus and a blur trigger for the input-mask element.
  • Add an active state for the button element.
  • Add a focus state for the select element.
  • Add an option to customize the font family for the select element.
  • Enable the binding of an array for the select element.
  • Make sure the select element triggers the workflow when using unselect.
  • Enable the reorganization of tabs & slides from the side bar for the tab and slider elements.
    All of the above should go live between next week and the end of June.
  1. Detaching modals from pages and making them accessible at project level: This will also go live tomorrow or Thursday. We’re currently putting the documentation together, and we hope you’ll like what we’ve built. We’re excited to hear your feedback so we can keep improving the new system on the fly.

  2. New organization of global workflows and edge functions + revamp of the plugins panel: This is currently in QA and is expected to go live around mid-June. Once released, it will also unlock the ability to create backend workflows for Supabase directly within WeWeb, using a no-code interface similar to our existing workflow builder. It’s an exciting improvement for Supabase users.

  3. Vite setup to reduce the build time: After running a few tests, we’ve decided to postpone the release. We identified a few areas that need improvement before going live. The release is now planned for mid-June, we’ll keep you posted as we get closer.

  4. We have the following fixes planned on the roadmap:

  • Fix the fact that the name is not saved when saving a template into the library - in production
  • Fix the calendar issue binding events - in production
  • Add a Help button to the top bar of the editor so users can easily access chat support - in production
  • Fix tooltips in the add menu (they are not displaying right now) - will be in production tomorrow or Thursday.
  • Fix the issue where changing the language on a dynamic page causes the parameter to become undefined - in QA, should be live soon.
  • Fix the input’s On enter event bug - in QA, should be live soon.
  • Fix the fact that the color property of icons from the ‘Phosphor Fill’ icon set does not work - in QA, should be live soon.
  • Fix a copy paste issue on the Code element (when pasting, the first character is not pasted) - under development, should be live in 2-3 weeks.
  • Fix the fact that it became impossible to create dropzone in components - under development, ETA TBD.
  • Make sure dropdowns can be opened in the datagrid - under development, ETA TBD.
  • Fix the fact that while setting the progress bar’s color the gradient color menu opens, while it should open the standard color menu - under development, ETA TBD.
  1. Other topics on the roadmap:
  • We’re implementing MFA (Multi-Factor Authentication) for accessing the WeWeb editor. It won’t be activated automatically for all users, but teams that want to enable it will be able to do so directly from the dashboard - should be live early June.
  • We are adding custom domain when connecting through SSO for Supabase - should be live late June.
  • Support & ticketing system: Our new ticketing system is live! We’re now using Intercom, which should make it easier for you to track the status of your tickets. We’re also revamping the ticketing app, the new version is expected to go live around mid-June. And last but not least, we’re super happy to welcome @rivan_sigarlaki to the team as a Customer Care Engineer, helping us further strengthen our support capabilities.
  1. Other topics under qualification:
  • SSR: Our exploration confirmed that this is technically feasible, which is great news. However, it would require about 4 months of roadmap from many of our developers to build. Given the effort involved, we’ve decided to postpone development for now and focus on other priorities. The good news is that we now have a clear understanding of what’s needed to make it happen, so we’ll feel more confident prioritizing it in the future. We will re-evaluate the opportunity in September.
  • Branching: Branching, in its current stage of qualification, is a substantial piece and is still under technical review. We’re not ready to share precise conclusions yet, but we do know it will require a significant development effort (we’re currently working to better estimate how long that will take). Once we have better visibility, we’ll keep you informed, but I suspect this will end up being postponed to later this year, for the same reasons as SSR. We know this feature is highly anticipated by many of you. Some large teams (>20 developers) have already found interesting ways to organize their workflows using smart substitutes for branching. To support you in the meantime, we’ll publish an educational piece this summer to help you structure team collaboration more effectively.
  • Figma plugin: this is under qualification, we hope to be able to prioritize it in the weeks to come. I’ll update you once we know more.

As always, feel free to comment and add your feedback in this thread in case you feel we missed something important!

19 Likes

Well done. Intercom sets the bar. And welcome @rivan_sigarlaki - I hope you have your helmet on :wink:

2 Likes

Raphael, thank you for the update!

Looking forward to the fixes and super excited about Gantt and Chat components!

3 Likes

@Raphael any chance we can get a quick glimpse of the Chat and AI Chat? Just wandering if I should spend time building this or it would be better to wait and see what you guys have come up with.

2 Likes

Hey @emdiemeric! :waving_hand:
Here’s a quick preview of the classic chat: Chat preview

There will be quite a few customization options, as you can see in the edit bar, and if anything is missing, it will be easy to fork the component and enhance it using WeWeb AI.
For the AI Chat, it will mostly be the same component but with a few specific options and actions to make it easier to connect to streamed variables, etc.

5 Likes

Hey, any intentions on enabling “custom” column in datagrid when the columns data is bind.