New range of wireframe components live in wireframe library 🚀

  • 3 November 2022
  • 26 replies
  • 1778 views

Userlevel 4

Hi Miro Fam 👋,

We have a cool new update for all you wireframe wizards. Miro now has 5 new wireframe components to take your collaborative wireframing to a whole new level!

 

 

From lists to cards, check out the whole range via the wireframe library. And don’t forget to add the library to your toolbar for ease of access. 🙃

Head to your Miro board and try it out! And don't forget to share your feedback with us here on Miro Communities. 

Happy wireframing!
Shubangi


26 replies

Userlevel 2

How can we add a column to the wireframe data table? There is no "+" available.

Userlevel 4

Hey @Frédéric Lebel Thanks so much for the note. We are working on optimizing the data table so will share this with the team!

Userlevel 1

Adding columns in the wireframe data table would be a great feature and will save a lot of time on prototyping!

Userlevel 1

+1 Adding column to wireframe data table.  Feature not usable in current state.

Userlevel 1

+1 for adding columns, this feature is not usable without it.

AND don’t forget to include deleting columns!

Userlevel 7
Badge +6

Just curious, why is the feature “not usable” without the ability to add and delete columns? I mean, it is for wireframing, after all. If it’s so important to have the exact amount of columns and rows in a simple wireframe, why not use the regular table? 🙂

Userlevel 1

Tables often have more than 3 columns, a regular table doesn’t have the pre-formatting that this feature provides.

Userlevel 7
Badge +6

@John Knowles Yeah, but again – it’s for wireframing. Wireframing is just a way to display the functional elements of an interface. I can see that being able to add columns is a nice-to-have, but I don’t quite understand why the lack thereof would render the entire wireframe component useless? 🙂

Userlevel 1

Ok, so its not useless if your interface has a functional need for a 3 column table.

Userlevel 7
Badge +6

I wouldn’t say it’s “useless” since it’s still just a simple visualization that should come with additional information. It’s a wireframe, not a blueprint. But I understand that it’s a nice-to-have.

Userlevel 1

It seems one persons nice to have is another persons should have in this case.

 

Suppose it depends on your design system, processes etc. Our wireframes need to contain all the functional parts of the feature/page/screen.


This data table component could save a good amount of time, if columns could be added to it, rows can be added after all.

If you applied the “no columns on tables” mentality to all the UI elements in MIRO it wouldn’t be as great as it is!

Hopefully MIRO will take this data table  MVP and make an MLP ;-)

 

Userlevel 7
Badge +6

It’s not a data table component though. It’s a data table wireframe component. ;) I still don’t quite understand why using the regular table — which is an actual data table component, not a wireframe component — isn’t an option here?

Userlevel 1

It is an option, but that data table component is not designed for wireframes.  Whereas the wireframe components are easier to work with, require less manipulation. 

Lets just agree to disagree 😅

Userlevel 7
Badge +6

Haha, you're right. I agree to disagree! 😄

It’s not a data table component though. It’s a data table wireframe component. 😉 I still don’t quite understand why using the regular table — which is an actual data table component, not a wireframe component — isn’t an option here?

 

Totally agreed with @John Knowles . It’s pretty useless.

I don’t use Data Table just for visual presentation. I need to label the columns. 
Same things goes to “text input” and “button”, they are meant for mocking visually, but without able to label them, it is useless.

 

 

 

Userlevel 7
Badge +6

@janet smith I still don't understand why it would be “useless”, that's a very harsh statement. Personally, I'd say it's highly ineffective to replace proper communication between people with detailed wireframes/mockups, but let's just agree to disagree! It's always interesting to discuss these things though. 😊

A is table bi dimensional, x and y. Having an option to add row and not columns is a bit odd to me.

@Henrik Ståhl I think it’s comments like yours above that cause stakeholders to acquire a distaste for lean agile.

Irrespective of your personal views on wireframing (and for what it’s worth, I agree), it’s for users to decide how they view / wish to use different system components. Ever seen that video of the QA sticking all the different shapes in the same shaped hole?

It’s not a data table component though. It’s a data table wireframe component. 😉 I still don’t quite understand why using the regular table — which is an actual data table component, not a wireframe component — isn’t an option here?

If the regular table is enough to build a prototype / wireframe, any reason why Miro creates a redundant component “data table” in the wireframe session?

Another request to add column, unusable in current form

Adding request for adding columns to data table

I’d like to revive this thread. 

 

My use case is designing a relational database. Each table in this relational database needs to show column names (fields), and a few example rows. 

The “Table” component is not a replacement for the wireframe “data table” because I cannot easily draw arrows showing the relationships between fields of different tables. (If there is, let me know please) 

Meanwhile, the “wireframe data table” has this capability. Unfortunately it does not allow me to add columns (fields) easily, which is extremely important for my use case. 

Adding request for adding columns to data table

+1 for adding and removing columns. It is significantly more difficult to get the point across to stakeholders if you constantly need to explain all their requested columns will be present in the final feature. 

I did a workaround by duplicating the datatable element :) but would love to see it as a feature. +1

Reply