Hmm … Better pigeon hole clients into only using the teabag.
“Why can’t I put the label in the water?!”
Smart developer: let’s make the label an 8 inch square so it won’t fit in any mug.
Developer: THATS IT WE’RE A BROWSER BASED APP NOW!
End user: why can’t I run this on my AOL account?
Huge waste of material on the label.
Since the labels are larger, the boxes for those tea bags will need to be larger too. That incurs in additional waste of material and storage space.
People working in markets selling those tea bags will complain. Now their boxes don’t fit in the aisle alongside boxes with tea bags of other brands.
Customers will find it clunky and convoluted. Some will understand why the dev did it, and get angry - because from their PoV it’ll sound like the dev is saying “I assume that you’re a muppet, unable to distinguish the label from the bag”.
And some will still do like others said: use a larger pot, fold the label, etc. Defeating the purpose of the change.
There are plenty situations where you can be smart. This is not one of them, stick to standards and document it properly. “This is the bag, it goes in. This is the label, it goes out.”
(Not that it changes much for me. I’m still ripping the tea bag apart and mixing the contents with my yerba mate. Unexpected use case!)
Just get rid of the label altogether. I’m always suspicious when a teabag has a string on it.
I design optics and I’ve seen a return request because they “couldn’t see the target” and included photos to show what they meant. The customer installed it backwards and didn’t bother trying the other way.
