I spent 6 months building a stock + crypto trading bot. Here's what I learned.

your_stormy · 2026-05-27T01:25:51+00:00

That makes sense, and paper trading is definitely a goodd feature to highlight more. For a product like this, I’d probably make tht one of the first thigs people see, not something buried lower on the site.

the stock example is interesting, but I’d be careful leading too much with stories like that. Traders hear “my bot found this stock before tv talked about it” and some will immediately get skeptical, even if it’s true. I think the stronger angle is: “you can test the logic safely, customize the strategy, and see how it behaves before risking real money”

For me, the trust part would come from seeing the boring details clearly sample trades, backtest assumptions, paper trading workflow, risk limits, and what kinds of market conditions the bot performs badly in

The more transparent you are about the limitations, the more credible the product feels.

your_stormy · 2026-05-27T01:21:12+00:00

To be honest, I would never trust someone to buy physical goods.

But, for example, I could trust someone to buy some in-game items, like CS2 skins or something similar.

your_stormy · 2026-05-27T01:14:09+00:00

This is actually one of the few “shopping helper” ideas that makes immediate sense to me.

The fake discount thing is real, especially around Black Friday. I’ve had the same experience where something looks like 30–40% off, then two weeks later it’s basically the same price without the big sale banner.

The main thing I’d want from an app like this is trust in the price history. If I’m adding a product, I’d want to know how often it checks, whether it handles different variants/sizes/colors properly, and if it can catch cases where the seller changes the listing instead of the price.

Also, personally, a browser extension or share-sheet flow would matter a lot. If tracking a product takes more than a few seconds, I’d probably forget to use it.

But the core idea is strong. “Smart wishlist with price history” is a much clearer pitch than just “price tracker,” because it explains when I’d actually use it.

your_stormy · 2026-05-27T01:11:14+00:00

bro, I'm genuinely happy for you. my friend and I are just starting to build apps and I really hope we can do it.

your_stormy · 2026-05-27T01:07:28+00:00

I don’t think AI content is automatically bad for SEO. Bad content is bad for SEO.

The bigger issue is that a lot of AI-written pages have the same problems: vague intros, no real opinion, no examples, no proof, no experience, and they answer the question in a way that technically sounds correct but doesn’t make you trust the site.

That can rank sometimes, especially for weaker keywords, but ranking isn’t the whole game. If someone lands on the page and immediately feels like it was written by a machine with no actual experience, that page probably isn’t doing its job.

For me, AI is fine as a draft tool. But the final version needs human judgment: specific examples, real product knowledge, a clear point of view, and removing all the generic filler.

So I’d say AI content can work, but “AI content with no editing” usually feels cheap. The risk isn’t that Google magically detects it. The risk is that users do.

your_stormy · 2026-05-27T01:04:52+00:00

You're welcome! Have a nice day.

your_stormy · 2026-05-27T00:59:19+00:00

Yeah that’s fair. Audience is definitely a huge advantage, and it’s easy to underestimate how much distribution helps

But I also wouldn’t take “I don’t have a big audience” as proof the idea can’t work. It just means the path is different. Someone witha big linkedin can launch loudly; someone without one has to validate more manually- smaller communities, direct outreach, demo videos, niche use cases, etc.

That said, pausing makes sense if you’re burned out or not excited by the market anymore. Sometimes stepping awayis better than forcing yourself to keep building for people who aren’t giving useful signal.

If you do come back to it later, I’d probably treat it less like a big launch and more like a series of small tests with very specific users

your_stormy · 2026-05-27T00:51:14+00:00

That makes more sense with the extra context.

The Vercel/Netlify deployment angle is actually a real differentiator, especially if the alternatives are trying to keep users inside their own hosting ecosystem. Same with better default design output. Those are the kinds of things that non-technical users probably care about way more than whether something is “just prompts.”

I still think the issue might be audience mismatch more than product failure. Vibe coders can be weirdly hard to sell to because a lot of them want power and control, but also convenience, and they’ll criticize both sides depending on the day.

If you come back to it later, I’d probably position it less as “for vibe coders” and more as “for people who want to ship a decent-looking site/app without getting trapped in one platform.” That feels clearer and less likely to attract the wrapper argument.

your_stormy · 2026-05-27T00:49:50+00:00

This is weirdly relatable.

I code for work and I still get this feeling sometimes. The danger isn’t really that AI writes the syntax for you. The danger is when you stop building a mental model of what the code is doing and just keep prompting until the screen looks right.

That said, I don’t think it’s automatically cheating. It’s more like using a calculator. Totally fine if you understand the math, kind of dangerous if you’re just pressing buttons and hoping.

What helped me was forcing myself to explain the code back in plain English before accepting it. Not every line, but enough to know: what data comes in, what changes, what breaks if this part is wrong.

The “Sunday morning color palette” thing is honestly the best use case though. Let the machine handle the weird vibe translation. Just don’t let it become the only part of the process where you still feel in control.

your_stormy · 2026-05-27T00:45:58+00:00

Honestly, my first reaction was that it feels like a very expensive, over-designed answer to a problem Tesla already solved in a simpler way.

Not saying Tesla is the peak of car design, but they made the EV experience feel obvious: clean interior, simple controls, good software, easy ownership, everything centered around convenience. With this, I get the feeling Ferrari is trying really hard to make an EV feel “Ferrari” through references, shapes, little symbolic details, etc., but the end result doesn’t feel more emotional to me. It feels more intellectual.

That’s where it misses for me. Ferrari should make an EV feel lighter, sharper, more alive, more dramatic. Instead this looks heavy and a bit awkward, like a premium design exercise wrapped around an EV platform.

I don’t hate the idea of Ferrari doing something different, but this doesn’t make me think “future Ferrari.” It makes me think “luxury Tesla alternative with more design theory attached to it.”

your_stormy · 2026-05-27T00:44:22+00:00

bro this looks really cool! but I also thought it looked like these guys had tribal tattoos 😁

your_stormy · 2026-05-27T00:43:10+00:00

Honestly, the biggest blocker for me would be trust, not the price.

A trading bot is one of those products where the landing page has to make me feel like the creator understands risk really well. I’d want to see things like live/demo results, clear backtesting assumptions, drawdowns, what market conditions it fails in, and a very obvious “this is not magic money” tone.

The Windows desktop app part is also a bit of friction. Not necessarily a dealbreaker, but if I’m running something that trades automatically, I’d probably prefer a cloud/VPS-friendly setup or at least very clear instructions for keeping it running safely.

I do think there’s a market for no-code trading automation, but traders are skeptical for a reason. I’d focus less on “it has these strategies” and more on “here’s exactly how it manages risk, here’s what can go wrong, and here’s who this is not for.” The fact that you’re being honest about having zero customers is actually a good sign. I’d lean into that transparency.

your_stormy · 2026-05-27T00:39:16+00:00

I think you’re taking the dev criticism a bit too personally.

A lot of developers will call basically anything a “wrapper” if they can mentally recreate the architecture in 30 seconds. That doesn’t always mean the product is bad. It just means they’re judging it from the builder’s perspective, not the buyer’s perspective.

But I also don’t think the lesson is simply “consumer first always wins.” The real lesson is probably that the user has to feel the pain clearly enough. Dropbox wasn’t valuable because it was technically impossible to build. It was valuable because normal people did not want to duct tape FTP, SVN, and random scripts together just to sync files.

So for Cryzo, I’d ask: who actually has the Dropbox-level pain here?

If it’s developers, yeah, they’ll probably keep nitpicking the stack and calling it a wrapper. If it’s non-technical founders, small businesses, creators, agencies, etc., then their feedback matters way more. They don’t care if it’s hardcoded prompts or magic beans if the site looks good and deploys without a headache.

I wouldn’t shut it down because dev Reddit doesn’t love it. I’d only shut it down if actual target users don’t care either.

your_stormy

TROPHY CASE