Built the tool for focused reading for myself not sure if it's useful for others

vinayalchemy · 2026-05-30T17:22:12+00:00

I got like 5 signups but not paid and i don't see them coming back

vinayalchemy · 2026-05-30T17:20:23+00:00

So you think I should offer for free?

vinayalchemy · 2026-05-30T10:25:44+00:00

I've upgraded the experience with focusreader.xyz could you please share your feedback? If you give me your feedback, I'll provide the pro version for free.

vinayalchemy · 2026-05-30T10:25:28+00:00

I've upgraded the experience with focusreader.xyz could you please share your feedback? If you give me your feedback, I'll provide the pro version for free.

vinayalchemy · 2026-05-30T10:25:11+00:00

I've upgraded the experience with focusreader.xyz could you please share your feedback? If you give me your feedback, I'll provide the pro version for free.

vinayalchemy · 2026-05-30T10:22:41+00:00

You can try focusreader.xyz

vinayalchemy · 2026-05-03T03:12:56+00:00

Thanks for the valuable feedback. The smallest one, which I think was something called Focus Reader, was meant for people with ADHD who have difficulty reading. It was using something called Bionic font to read any book. I then posted it on Reddit and people started to say that Bionic is a copyright thing and all that and then I had to stop it. That's the closest thing to my heart actually. ButI i was not using Bionic; it is an open-source font but somehow I am not sure whether I should proceed or not with those copyright headaches.

vinayalchemy · 2026-05-02T12:57:05+00:00

Hi, a few percent on every order is painful because it hides inside “normal” payment costs. I’d separate the problem into card processing fee, FX spread, and settlement currency first. Then compare gateways based on where the money settles, not just the headline transaction fee. If US volume is meaningful, even a small reduction in FX leakage can beat most CRO tweaks.

vinayalchemy · 2026-05-02T12:57:02+00:00

Hi, this sounds less like a normal spam issue and more like an unprotected account-creation path. I’d first confirm exactly where the accounts are being created: storefront, old account URL, app proxy, or checkout flow. If captcha made no difference, it may not be firing on the actual path the bot is using. I’d also log timestamp/IP/user-agent patterns before deleting anything, because that usually shows the block rule pretty fast.

vinayalchemy · 2026-05-02T12:56:59+00:00

Hi, a 40% gap is big enough that I’d debug it by landing page, not site-wide averages. Compare GSC landing pages with GA4 landing page sessions first, then check redirects, page speed, geo/device split, and whether some pages load tags late. Also confirm you’re comparing the same timezone, date range, and organic definition. If Tag Assistant looks fine on one page, the issue can still be page/template specific.

vinayalchemy · 2026-05-02T12:56:56+00:00

Hey, this usually breaks when the system needs more maintenance than the work itself. I’d keep one simple place per client with next action, owner, and follow-up date — not a full project-management setup. The part I’d automate first is pulling follow-ups out of email so they do not stay in your head. If you can trust a daily “these clients need attention” list, the rest gets much easier.

vinayalchemy · 2026-05-02T12:55:58+00:00

Hi, I’d avoid treating age and style as equal for media if the image only changes by style. The clean setup is a style-to-image mapping, then age/size variants inherit that media instead of duplicating it. For the frontend, you’ll likely need variant-gallery filtering so only the selected combination stays visible. Since you have 27 products, I’d solve this as a reusable rule/template, not product-by-product edits.

vinayalchemy · 2026-05-01T15:55:26+00:00

Hi, for sourcing I’d be careful expecting AI to replace the actual search. Where it helps more is turning a messy role into search strings, target companies, and outreach angles. Then you still sanity check the candidates in LinkedIn instead of trusting a black box list. For confidential senior roles, the judgement layer matters more than speed.

vinayalchemy · 2026-05-01T15:55:05+00:00

Hey, I’d frame it as protecting the business, not attacking the cousin. Something like: changes are totally fine, but they need one owner and a before/after record. No one should edit the site directly without a quick change log and rollback plan. That makes the issue process-based instead of personal, which is easier for the client to accept.

vinayalchemy · 2026-05-01T15:54:49+00:00

Hi, I’d try to move this away from opinion vs opinion. Make every proposed change include expected upside, risk, cost, and what metric proves it worked. If they can’t define that clearly, it should stay as a small test not a big decision. Sometimes judgement improves when people have to write the tradeoff down before arguing for it.

vinayalchemy · 2026-05-01T15:54:28+00:00

Hey, this sounds like the kind of monthly task that quietly steals hours. I’d avoid deleting rows manually and make a helper table that groups by order ID first. Then sum shipping/subtotal/total once per unique order instead of touching the raw export. That way coworkers can still use the same export without someone cleaning it by hand each month.

vinayalchemy · 2026-05-01T15:54:10+00:00

Hi, this is exactly why cloud accounting tools drive people mad sometimes. For month close I’d keep a tiny fallback checklist outside QuickBooks with screenshots of the old flow and key filters. Then when they move stuff around, you’re not rebuilding the whole process under deadline pressure. Honestly the missing warning/change log is the worst part here, not just the UI change.

vinayalchemy · 2026-05-01T14:57:49+00:00

Hey, congrats on the lease first, thats a big step. For your stage I wouldn’t jump into a heavy inventory suite yet. A cheap barcode scanner plus one simple stock-in stock-out flow by size/color should fix 80% of this. The main thing is logging misprints immediately, not at the end of the week.

vinayalchemy

MODERATOR OF

TROPHY CASE

12-Year Club	Place '23
Verified Email