3 ms·

https://veneer.leftium.com https://veneer.leftium.com is a similar project: a thin layer over Google sheets/forms: - Adds markdown support - Makes it prettier

by Leftium 9mo ago

https://veneer.leftium.com https://veneer.leftium.com is a similar project: a thin layer over Google sheets/forms: - Adds markdown support - Makes it prettier, especially on mobile - Adds open graph social sharing image/title Based on actual convention used by (dance) groups in Korea to use Google forms for event sign ups. It doesn't require changing their workflow: the original forms still work (as a fallback), they just need to share a different URL based on the form ID. I've shown Veneer to several dance group organizers who use these Google forms on a regular basis. While two people have embraced the concept and registered their custom domains for their forms most people are surprisingly hesitant to use Veneer. Objections I've heard: - Already have a workflow; don't want to learn something new - Know how to program themselves, can make themselves if needed - Already registered an unused domain, but have other plans for the site - Prefer simple (even though I simplified: https://red.leftium.com https://red.leftium.com) Each Veneer page has a link to the original Google form and sheet. (Also a link to the full MIT-licensed source.) Here is the only one that is "in production:" https://viviblues.com https://viviblues.com

paravaib 9mo ago
This is a really useful data point, thanks for sharing it. The hesitations you listed line up closely with what I’ve been seeing too — especially “already have a workflow” and “prefer simple”. It feels like most resistance isn’t about capability, but about introducing anything that feels like a new tool, even if it’s thin. That’s actually the tension I’ve been trying to solve as well: keeping the original workflow completely intact, and making the public layer feel more like a passive view than something you have to “adopt” or manage.

by Leftium 9mo ago

paravaib 9mo ago

This is a really useful data point, thanks for sharing it. The hesitations you listed line up closely with what I’ve been seeing too — especially “already have a workflow” and “prefer simple”. It feels like most resistance isn’t about capability, but about introducing anything that feels like a new tool, even if it’s thin. That’s actually the tension I’ve been trying to solve as well: keeping the original workflow completely intact, and making the public layer feel more like a passive view than something you have to “adopt” or manage.