# What Features Do You Want to See in Weweb This Year?

**URL:** <https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796>\
**Category:** Ask us anything\
**Created:** [February 24, 2025, 10:06am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796 "2025-02-24T10:06:14Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![bradley\_gibson](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/bradley_gibson/32/10492_2.png) [@bradley\_gibson](https://community.weweb.io/u/bradley_gibson)\
**Post date:** [February 24, 2025, 10:06am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/1 "2025-02-24T10:06:14Z")

</div>

As we approach the conclusion of the V3 rollout, with just a few bug fixes remaining, I’d like to hear your thoughts on what features you’d like to see next.

One enhancement I would love to see is a versioning system similar to what Flutterflow provides. This would allow us to work on major updates while still addressing bugs in the main branch, enabling us to fix issues without the pressure of immediately publishing the larger update.

What do you think?

---

<div class="post-metadata">

**Author:** ![bongoumedia](https://avatars.discourse-cdn.com/v4/letter/b/8e7dd6/32.png) [@bongoumedia](https://community.weweb.io/u/bongoumedia)\
**Post date:** [February 24, 2025, 10:28am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/2 "2025-02-24T10:28:59Z")

</div>

Same, branching would be wonderful

---

<div class="post-metadata">

**Author:** ![Corner](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@Corner](https://community.weweb.io/u/Corner)\
**Post date:** [February 24, 2025, 11:39am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/3 "2025-02-24T11:39:16Z")

</div>

Not really a huge feature, and I don’t know if that’s possible, but I would love being able to retrieve previous filters that aren’t working for some reasons (rn they become grey and no choice but to delete them to set up new ones):

 ![Capture d'écran 2025-02-24 123710](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/6/653867079680d9ee27724c7ed96aef084738d9e0.png)

---

<div class="post-metadata">

**Author:** ![sam1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/sam1/32/6724_2.png) [@sam1](https://community.weweb.io/u/sam1)\
**Post date:** [February 25, 2025, 4:04am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/4 "2025-02-25T04:04:48Z")

</div>

This typically happens when the field that your referring to hasn’t correctly loaded in or has no data in it

---

<div class="post-metadata">

**Author:** ![Corner](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@Corner](https://community.weweb.io/u/Corner)\
**Post date:** [February 25, 2025, 9:37am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/5 "2025-02-25T09:37:27Z")

</div>

Yep that’s right, but what I would like is at least to see the broken filter, to know what to change

---

<div class="post-metadata">

**Author:** ![Corner](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@Corner](https://community.weweb.io/u/Corner)\
**Post date:** [February 25, 2025, 9:39am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/6 "2025-02-25T09:39:14Z")

</div>

Regarding features, what about a Despia integration ? Not saying this is THE thing, but to have a quick MVP of a mobile app, looks nice

---

<div class="post-metadata">

**Author:** ![pauldev](https://avatars.discourse-cdn.com/v4/letter/p/b5ac83/32.png) [@pauldev](https://community.weweb.io/u/pauldev)\
**Post date:** [February 25, 2025, 10:28am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/7 "2025-02-25T10:28:02Z")

</div>

I don’t really like flutterflow’s branching. I tried it, but the work I did wasn’t copied. I had to do it again or copy and fix it page by page. Actually, to solve the problem of major bugs, we should also do the staging of the system, which is a beta version and let users test it first. If there are no problems, we will upgrade to the production version.

The features I want to see are:

1. AI that helps write formulas or JS like before

2. SEO or SSR because if a website cannot support SEO, what’s the point if people can’t find it? And the page title cannot be changed to the dynamic data. When people bookmark and share on social media, the names are all the same, which doesn’t look professional.

3. If point 2 doesn’t work, at least find a way similar to SSR without having to be real-time, such as generating an HTML page from a dynamic page without having to create a new API or create a new page in multiple steps.

4. Contact form plugin that can edit the sender’s email that is not a weweb email.

---

<div class="post-metadata">

**Author:** ![carrano\_dot\_dev](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/carrano_dot_dev/32/10547_2.png) [@carrano\_dot\_dev](https://community.weweb.io/u/carrano_dot_dev)\
**Post date:** [February 25, 2025, 11:09am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/8 "2025-02-25T11:09:26Z")

</div>

Dynamic environmental variables (so that I can set up my supabase client to switch credentials b/w staging/prod), branching, unit testing, execute component workflows directly with javascript, custom fields in the new datagrid, recaptcha 3, ‘run code’ button in the js editor window

---

<div class="post-metadata">

**Author:** ![caffeinatedwes](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/caffeinatedwes/32/625_2.png) [@caffeinatedwes](https://community.weweb.io/u/caffeinatedwes)\
**Post date:** [February 25, 2025, 1:32pm UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/9 "2025-02-25T13:32:52Z")

</div>

+1 to branching

---

<div class="post-metadata">

**Author:** ![julian](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@julian](https://community.weweb.io/u/julian)\
**Post date:** [February 25, 2025, 2:24pm UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/10 "2025-02-25T14:24:12Z")

</div>

- Enable **different Supabase instances for editor, staging and production** to have a proper deployment process
- **custom fields** in the new datagrid

---

<div class="post-metadata">

**Author:** ![frenchdetailers](https://avatars.discourse-cdn.com/v4/letter/f/cc9497/32.png) [@frenchdetailers](https://community.weweb.io/u/frenchdetailers)\
**Post date:** [February 26, 2025, 9:57am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/11 "2025-02-26T09:57:00Z")

</div>

+1 Improve SEO

---

<div class="post-metadata">

**Author:** ![despia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/despia/32/12626_2.png) [@despia](https://community.weweb.io/u/despia)\
**Post date:** [February 26, 2025, 3:47pm UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/12 "2025-02-26T15:47:36Z")

</div>

We already nicely integrate with WeWeb - Despia works natively with Vue JS (which is what WeWeb uses) - but it requires copy / pasting some code, which should be pretty simple - and we are happy to help and answer any questions along the way.

Here is a little video about the integration process: [https://youtu.be/gXYpFN87WuU?si=WoyodkjYoWmmOSi0](https://youtu.be/gXYpFN87WuU?si=WoyodkjYoWmmOSi0)

---

<div class="post-metadata">

**Author:** ![Corner](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@Corner](https://community.weweb.io/u/Corner)\
**Post date:** [February 26, 2025, 3:48pm UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/13 "2025-02-26T15:48:41Z")

</div>

+1 improve SEO

---

<div class="post-metadata">

**Author:** ![CedricFR73](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/cedricfr73/32/6618_2.png) [@CedricFR73](https://community.weweb.io/u/CedricFR73)\
**Post date:** [February 27, 2025, 1:25am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/14 "2025-02-27T01:25:22Z")

</div>

- I would like to see some elements that are a bit more dynamic. For example, a calendar with more display options (months in columns from the 1st to the 31st) and drag & drop features (preconfigured event divs with time slots, colors, etc., that can be directly dragged into the calendar element). Events should be editable on the fly, with handles to extend or shorten a time period.

- Additionally, an element that allows easy PDF generation from the front end.

- Fully integrate Xano into WeWeb to have a single interface, allowing seamless management of Xano workflows just like WeWeb workflows and ensuring perfect error handling for Xano.

- Better handling of nested iterations (purple parameters).

- Ability to add indentations when creating “formulas,” similar to simple text editors.

For example:

```auto
switch(expression,  
    Value 1, Result 1,  
    Value 2, Result 2  
)

```

Instead of:

```auto
switch(expression, Value 1, Result 1, Value 2, Result 2)

```

In very large formulas, this would make readability and organization much easier.

---

<div class="post-metadata">

**Author:** ![Himanshu](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/himanshu/32/16305_2.png) [@Himanshu](https://community.weweb.io/u/Himanshu)\
**Post date:** [February 27, 2025, 5:47am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/15 "2025-02-27T05:47:05Z")

</div>

+1 for branching

---

<div class="post-metadata">

**Author:** ![Micah](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/micah/32/9102_2.png) [@Micah](https://community.weweb.io/u/Micah)\
**Post date:** [February 27, 2025, 6:28am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/16 "2025-02-27T06:28:15Z")

</div>

Branching!

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [February 27, 2025, 7:18am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/17 "2025-02-27T07:18:36Z")

</div>

I don’t think we’ll see branching any time soon, at least not by December / next year because of the AI 😄

---

<div class="post-metadata">

**Author:** ![TriGemini](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/trigemini/32/13013_2.png) [@TriGemini](https://community.weweb.io/u/TriGemini)\
**Post date:** [February 27, 2025, 9:18am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/18 "2025-02-27T09:18:58Z")

</div>

Of course all mentioned functionality - but I’d like to see more **useability improvements on the IDE** itself e.g.:

- Tooltips on various parts of the “IDE”

- Search functionality in properties pane (just as in the layout pane)

- Long page names are hard to work with, as various parts just hides the last parts  
(e.g. when linking to a page with a long name). Could either be solved by tooltips  
or maybe making the right property pane resizeable by the user.

- Pages in folders - folders should be displayed everywhere lists of pages in the UI are.

- Make “right property pane” collapsible

- Improve insertion of elements in the layout tree - dragging into the right place can a pain

- Multiple selection of elements in layoutpane for delete/copy/paste

- Make it possible to cancel a drag operation in the layout pane. When starting a drag you  
have to drop it - would be nice if you could just press escape.

---

<div class="post-metadata">

**Author:** ![kavi](https://avatars.discourse-cdn.com/v4/letter/k/a88e57/32.png) [@kavi](https://community.weweb.io/u/kavi)\
**Post date:** [February 27, 2025, 9:43am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/19 "2025-02-27T09:43:08Z")

</div>

Dynamic Breakpoints

---

<div class="post-metadata">

**Author:** ![oli](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/oli/32/8397_2.png) [@oli](https://community.weweb.io/u/oli)\
**Post date:** [February 27, 2025, 10:45am UTC](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796/20 "2025-02-27T10:45:00Z")

</div>

Another +1 for branching please 🙂

[Next page](https://community.weweb.io/t/what-features-do-you-want-to-see-in-weweb-this-year/16796.md?page=2)
