Receiving feedback is not the same as having permission to publish it.
That distinction shaped ReviewDesk, a customer feedback and testimonial system I designed and built at Noerong.
For a local business, the workflow starts after a completed job: request honest feedback, keep track of the response, and make the next step clear.
Three decisions shaped the experience:
1. Keep the customer journey focused.
A branded page and private request link make it clear where to respond. Scheduled reminders stop after a response.
2. Separate feedback from public proof.
Testimonial consent and administrator approval are distinct steps. Every rating receives the same public-review option, without filtering out unhappy customers.
3. Give the business a useful overview.
The dashboard brings requests, responses, activity, and approval status together. Approved testimonials can appear on a public wall or an embeddable website widget.
I designed and developed the customer flow, dashboard, reminder worker, and widget using Python and FastAPI.
The loop shows the feedback page, business dashboard, and testimonial wall. All customer names, comments, and metrics are fictional demo data. The public demo sends no email and retains no visitor submissions.
The detail I care about most: permission is part of the product, not an afterthought.
Hey, it’s been a while since my last update. I’ve been focused on a few projects behind the scenes, but I’m back with a major Weave milestone.
Weave helps professionals exchange time and expertise using Skill Hours instead of money.
My last update covered the invite application system. Since then, I’ve built:
Authentication: Secure account access with Firebase.
Onboarding: Guided profile and skill setup.
Profiles and portfolios: A place to showcase work, skills, and trust.
Member dashboard: A clear view of activity and ongoing work.
Admin dashboard: Tools for managing users and community health.
Skill Hour Ledger: Tracks every hour earned, spent, or transferred.
Marketplace: Members can publish requests and find collaborators.
Cloud infrastructure: Neon for data and storage, prepared for Cloudflare Workers.
Today’s milestone is the Exchange Workflow, the system connecting everything.
Members can now move from an accepted application into a dedicated workspace, communicate, share files, track milestones, submit deliverables, complete the exchange, transfer Skill Hours, and leave reviews.
The core Weave experience is finally taking shape, and I’m excited to share what comes next.
The milestone view makes the workflow feel tangible—especially the clear split between deliverables and activity. Nice product thinking in how you surface progress without adding noise.