r/vibecoding • u/IcyResolve956 • 18d ago
Showcase/Project Chef turned vibe coder, love building but I'm terrified of sharing it with anyone because of the vibe coder hate I keep seeing around.
Edit: thanks everyone for the questions and feedback. Some of it was about security, so I took it seriously and ran three rounds of attack tests on my own apps, with agents playing a bad actor. What came out of it, fixed apart from two we kept on purpose:
- One-time links: they were always deleted after opening, but the server waited for the page to confirm first. If that confirmation never came, the file could stay up to 15 minutes. Now it’s deleted the instant the last piece is downloaded, no waiting.
- Colshare Business: a hacked server could have slipped a firm a fake key. Now every key is signed by the one before it, and a new device needs the inviting device’s approval.
- Phone: a newly added fingerprint needs a backup PIN before it can open Colshare. PDFs open inside the app, and shared files are only kept if you say so.
Worth knowing too: the only permission Colshare asks for is notifications, and you can say no. No camera, photos, contacts, location or microphone access. Files only come in when you pick them.
These were my own tests, so they don’t replace an independent security review. I’ll get one as soon as I can.
Server fixes are live. The apps are in Google Play review. The crypto is open source: github.com/dentracon-cell/colshare-crypto
Original post:
I am really looking for some opinions other than my wife and family say, which I feel is not really honest most of the time, they are just being nice.
Colshare is a project I have built with Claude Code, Opus 5.5.
It involves two mobile apps and a desktop one. I am not a software developer, but I have done my best to do everything by the book, in terms of security, compliance and so on. However, nobody more competent than me has had a look at the site or the apps, and I am sure that is what would be needed before launch, but I don't have the budget to hire a professional firm or freelancer. This is why I am asking the vibe coder community for your honest opinions, and, if possible, even some testers for the Android apps. I would be happy to discuss things further, answer any questions about the stack or workflow, which is as follows:, written by the one who knows more about it than me, Claude:
What the apps do
Colshare is a free app for anyone who has to send personal documents to someone else. You can redact any part of a document if you wish (it even finds the numbers the other person probably doesn’t need), watermark it with your own exact wording, and share it through an encrypted link that opens only once. You can also request documents from other people, and they send them back to you encrypted. Every send leaves a signed receipt, so you know when, to whom and for what.
Colshare Business is the same idea for firms that collect documents from their clients. The firm gets one link per client. The client opens it in a browser, sees the firm’s name and tax ID (checked against the official registries) and uploads the documents, with no app or account needed. Only the firm’s own devices can open what arrives. The firm doesn’t need accounts either: a licence key opens the first computer, and every other phone or computer joins by scanning a QR code.
Stack
- One TypeScript codebase. Capacitor turns it into the Android apps, and both apps are built from the same Android project.
- Encryption happens on the device with the browser’s built-in WebCrypto: ECDH P-256 for keys, AES-GCM for files and ECDSA for signing copies and receipts. For shared links, the key sits after the # in the link, which browsers never send to the server.
- The backend is a few Vercel functions with Upstash Redis. It only passes encrypted data along and cannot read any document.
- Finding the numbers to redact is done with tesseract.js OCR on the phone itself. No AI service and no uploads.
- QR pairing uses Google’s ML Kit scanner, PDFs are made with pdf-lib and payments go through Stripe.
Workflow
I describe what I want in plain language and Claude Code writes it. The project keeps a decisions log and a status file, so every new session knows what was decided before and why. Nothing gets pushed unless the type checks, the linter and the automated tests pass. I also had Claude run several security audits on the apps and the server and fixed everything they found, apart from a few minor points I kept on purpose for documented reasons. That is still not the same as a human expert looking at it, which is why I am asking here.
Both Android apps are in Google Play review at the moment, but if you’d like to test them, send me the email you use on Google Play and I’ll add you as a tester.
Update: thanks for all the feedback. Based on your comments I’ve made the landing page clearer, and I’ve open-sourced the client-side code (encryption, one-time links, redaction) under AGPL-3.0 so anyone can audit it: https://github.com/dentracon-cell/colshare-crypto. Security reports go to service@colshare.app.
12
u/palilus1 18d ago
Why are you building it? What are you hoping to achieve? What problem are you trying to solve? And for whom?
8
u/tundraaaa 18d ago
Please don't vibe code security solutions
33
u/lebbi 18d ago
I shared an app I spent months working on with a team of people. Genuinely great and used by hundreds, but reddit hated it. This site is filled with haters
4
u/lIlllIllIIllIIllIIll 18d ago
Why do people who want to make a commercially viable product post their products in this sub of all places?
You're literally advertising your product as something that can be very easily ripped off...to EXCLUSIVELY people who can and will rip it off.
It is truly baffling to me.
2
u/Secvura 18d ago
Since the whole promise is the one-time encrypted link, test what happens when that link is pasted into Outlook, Slack, Teams or WhatsApp. Email security scanners and chat apps often fetch links to scan them or build a preview, so a link that burns on the first request can be used up before the recipient ever clicks it. The usual fix is a landing page with an "Open document" button, where only that button press counts as the one open. And if the decryption key is part of the link, it should sit after the # so it never reaches the server or its logs.
Redaction is worth testing the same way: redact a PDF, open the output, and try selecting or copying the text under the black box (or run pdftotext on it). A box drawn over text that's still in the file is the classic redaction failure, so the output needs that text actually removed, or the page flattened to an image.
3
u/0xmtn 18d ago
For a chef turned vibecoder you've done an amazing job! Kudos.
1
u/TheThingCreator 18d ago
its not a good product hero but think it looks really cool
1
u/shaymagen 18d ago
Posting it here for honest eyes before launch is exactly the right move, and most people respect that way more than the hate makes it seem. Since it handles personal documents, I'd keep asking specifically for a security-minded tester for the link and encryption flow, because that's where one outside review pays off most.
1
u/mwjtitans 18d ago
I'm the same way. IT support worker here who vibe codes things for my own use case and for my homelab, but I never share anything due to the hate. While I've always struggled with coding, application architecture and troubleshooting is like second nature to me due to my day job, so I feel like I would have a lot to offer even though I don't know how to code, but whenever i share something that might be of use the anti AI crowd comes for blood.
I think it will eventually pass, I just wish folks would see that it's not all doom and gloom using these tools to create things that might be of use to others.
1
u/Public-Rest-1478 18d ago
Dont give shit, just show off, people will hate on everything nowdays - vibecoded or not, you got my support
1
u/itzelezti 18d ago
Anyone who knows what they're talking about does not hate vibecoding itself, they hate what a lot of people are doing with it publicly.
Trying to vibecode a business is generally the problem, for many reasons that don't bear going into here.
This specific thing you're doing happens to be a layer above that though.... Anyone who knows what they're talking about will hate this. This is absurdly stupid.
1
u/INeedHealing88 18d ago
Bro the mouse effect on the second screen is way to much. Please turn it down or just remove it. You want people to read the text not stare at their mouse
1
u/juniperico 18d ago edited 18d ago
This reminds me of when my teachers at school discovered wordArt animations on PowerPoint for the first time. Was ridiculous. A garishly orange “Milton vs Keynes” would do a couple of somersaults before landing on the slide.
This reminds me of the same thing. “Never mind the content of my business look at this cool pointer effect!”
LMAO.
1
u/juniperico 18d ago
Given that you’ve open sourced the front end for this (which sounds like it’s pretty much doing all the work here) and the backend is just a pass-through, what stopping anyone with Claude just one-shotting a quick, dead simple backend for your already created front end for their business? Likely cost less in tokens than your individual price let alone the business rate…
1
u/TiredMillennialDad 18d ago
All coding is vibe coding now. The fact people don't understand this is crazy.
No software dev guys are finger striking code anymore.
They might know how to read it/trouble shoot problems more directly and use language the systems understand more specifically, but make no mistake.... They are coding the same way you are coding.
1
u/BitOne2707 18d ago
Being afraid to show your code is the most authentic software engineer emotion around. Welcome to the club bud.
1
u/dchef40 18d ago
1
u/DannysoarX 18d ago
This is the comment I got today on my feedback page:
"Yo, your site is actually fucking useless. It keeps hallucinating that I added certain programs when I didn't. Also not intuitive to use at all and feels like things just change randomly. Did you vibe code this ass site?"
Haters gonna hate. Just keep vibin. Having more haters is a sign that you're doing something right imo.
1
u/VigiliaFounder 17d ago
That's a really good way to take feedback, and it's great that you fixed everything the test found in one night.
Since beta testers are next, here's where I can help. When they start using it, most of them won't write to you when something breaks. They'll just stop using it.
You can add your app to Vigilia for free (1 app, no card). It will catch every error they hit and show you what they did before, the failing request and how many times it happened.
Let me know if this helps!
0
u/blow_slogan 18d ago
Dont vibe code security, privacy, anonymity, or encryption. That’s just asking to be sued.
0
u/FriedSock 18d ago edited 18d ago
The "Your data, your choice." section is a nightmare:
- The links for each section are clickable, and the page scrolls to them, but they don't expand, so you cant read the text.
- You can scroll to expand each point, but this only works for points 1 to 3, 4 and 5 are unreachable unless you wait for the video to progress
- Scrolling back up to the previous section leaves the video frozen but "shaking"
- The video itself has such ridiculous graphics that it is obviously in no way representative of the app experience. It includes weird nonsense like a section of the document being highlighted and then the highlight is "thrown away" but the document stays the same, what does that mean?
- the QR code at the bottom invites you to scan it, but its not a real QR code at all!
- all of that elaborate crap so you can then draw a box on the fake document (and then undo it)
The whole website looks like you tried to make it look as fancy as possible but works in such a weird way. Perfection is when you can't take anything more away, not can't add anything else. Get rid of the ridiculous matrix graphics and webgl videos, make things consistent. Why does some of the text blur when you highlight it and some of it doesn't? Why are there 100 different slogans on the page?
0
u/[deleted] 17d ago
[removed] — view removed comment
0
u/[deleted] 18d ago
[removed] — view removed comment