Use what works. Build what's missing. Share the results.
We're forced to use tools we didn't choose — locked-down systems at work, ad-supported apps at home — and we feel the friction every day. That quiet frustration of something we know could be better — if only someone would fix it already! That used to mean filing a ticket and waiting for someone to care. Not anymore. ShadoLogiq Labs is an exercise in user-experience-first labwork, where "we" means us, the users — because AI now puts real power in our hands. What's here is only the beginning. The launcher below is something one of us built (with a ton of AI help) — re-skin it, resize it, right now.
A tool one of us built with AI — running right now
Gapps Embed · themed via three URL params · runs entirely in your browser
Try a theme:
How we work
Three things we stand on
A good experience is our right, not a privilege
If we have to work in something all day, it needs to work for us — not against us. Bad defaults aren't a law of nature; they persist because the people who own the platform rarely feel the friction we live with. They ship the roadmap; we live with the gaps. We're done waiting for that to trickle down — so we close the gap ourselves, two ways: use the tool that already gets it right, or build the fix that doesn't exist yet.
AI doesn't replace us — it empowers us
We're not professional developers — we're users, and we can learn, in real time, what AI makes possible. Our fear is natural: we fear what we don't understand. But there's only one way to understand AI — use it to do something we didn't think possible. It won't replace us; it replaces the excuses we've all grown tired of: I'm not technical, that's not my job, there's no time, IT would never approve it. Judgment and taste stay ours; synthesis and scale are on tap. The only way to shrink the fear is to understand the power — so leverage what some of us have already done, and join us on the journey.
We don't wait for someone else's timeline
No deploy window, no roadmap, no backlog to sit in. We build it local, prove it works for ourselves, and only then work to share it. That's the part that compounds: it's not just us + AI anymore — it's us, AI, and each other. One person's proven fix becomes everyone's starting point — on our schedule instead of someone else's.
What we vet & use
We vet and use what already works.
When an app or tool already delivers good UX, we don't rebuild it — we run it through a written checklist and spell out exactly why it earned its spot as a pick. Every entry carries a Spark-Vetted seal with a grade and a re-review date.
Vetted doesn't mean perfect — it means an honest place to start. Every grade names the caveats out loud, because most of what we pick is good enough to use and still has something worth fixing.
And safety isn't optional. Nothing earns a spot if it quietly watches what you do, sends your information off somewhere, or puts you at risk. The bar is simple: would we hand it to a friend?
22 vetted · 13 turned down · every rejection public, with its reason.
Often "missing" starts inside something we already live in. Google Workspace is where a lot of us start — handed to us, not chosen. We're honest about it: we'd never list it as one of our picks, but most of us can't simply walk away from it either. And it gives no clean way to drop an app launcher into an intranet page and get people to the right tool fast. So we built Gapps Embed. That's the pattern: a tool we already use gets us most of the way, and we build the last mile. (SNapp Extension is in rebrand; more are queued.)
A tool we'd use if only one thing were fixed isn't a dead end — it's where the next build starts. And once it's built, the hard part is getting it into each other's hands — so we share the results, without the usual store gauntlet.
What we build runs on your own computer, not someone else's — nothing gets sent off, nobody's keeping tabs, and no one can switch it off or start charging for it later. This was never about making money; it's about fixing what bugs us, safely, and handing the fix to the next person.
For the first time, the tools to fix bad software are in our hands — and a lot of that capability is free. The same AI that helps us draft an email can help us build the fix we spent years waiting for someone else to ship. The instinct nagging at us about a tool that should be better? That's the raw material.
That's the whole loop: use what works, try a fix of your own with the AI you already have, learn that you can actually do this — and if it turns out well, share it so the next person gets a head start instead of starting from scratch.
By users, for users.
We've always been told we matter — that our feedback counts. And maybe it does — but we were still one voice against priorities that were never ours, whether the gatekeeper was a vendor, an IT department, or a backlog no one staffs. Here's what's actually different: this isn't a promise to listen better. The equalizer is AI done right — we stop waiting to be heard and start holding the lever. We badger the model until it gets the fix right. (It might even cop an attitude with us. We get it right anyway.) That's not a support queue we're stuck in — it's a tool in our hands. We hope what's here already earns its place — but it's only the beginning, and it gets better the moment you join the we. Don't file a ticket. Rewrite the logic.
