Honest ask
There are so many UI libraries out there. But what few things you as a developer, designer feel missing on these libraries ?
What would you like to see in these AI generated websites era?
I am building an UI library though I know there are lots of libraries in the market. But I want to know is there any gap on which a UI library can be made.
My initial wish is to build somethings useful not only fancy stuff.
Here is so far that has been built https://www.craftui.space/
I will be very thankful if you give some ideas or critique my design skills ( I am learning actually )
I want to make money if possible and want to be design engineer.
Honest ask
There are so many UI libraries out there. But what few things you as a developer, designer feel missing on these libraries ?
What would you like to see in these AI generated websites era?
Payment Modal based on morphing technique.
The same button morphs into a payment modal. Height is animated based on inside content using `react-use-measure`.
- Used framer motion for animating the content inside card with opacity , blur and y animation
variants={{
initial: { opacity: 0, filter: "blur(4px)", y: 8 },
animate: {
opacity: 1,
filter: "blur(0px)",
y: 0,
transition: {
duration: 0.42,
ease: [0.165, 0.84, 0.44, 1],
},
},
exit: {
opacity: 0,
filter: "blur(4px)",
y: -4,
transition: {
duration: 0.15,
ease: [0.55, 0, 1, 0.45],
},
},
}}
initial="initial"
animate="animate"
exit="exit"
- used https://ui.bklit.com/docs for chart library. It has beautiful components of chart for ready to use.
- Used framer motion for animating the content inside card with opacity , blur and y animation
variants={{
initial: { opacity: 0, filter: "blur(4px)", y: 8 },
animate: {
opacity: 1,
filter: "blur(0px)",
y: 0,
transition: {
duration: 0.42,
ease: [0.165, 0.84, 0.44, 1],
},
},
exit: {
opacity: 0,
filter: "blur(4px)",
y: -4,
transition: {
duration: 0.15,
ease: [0.55, 0, 1, 0.45],
},
},
}}
initial="initial"
animate="animate"
exit="exit"
- used https://ui.bklit.com/docs for chart library. It has beautiful components of chart for ready to use.
Hi everyone,
I’ve been working on a Slack app that transforms your Slack workspace into a fully functional customer support chat. The idea came from the frustration of constantly switching between tools like Intercom/Zendesk for customer messages and Slack with per agent pricing.
With this app, you can:
• Handle customer support in one place. Support@domain.com goes to #support, billing@domain.com goes to #billing. Every conversation is saved stored and ready for ai analysis to fix bugs, content creation, blog post
• Integrate live chat in website and chat from slack
• Simplify your workflow by saving pre filled responses and use them,.AI auto tags every tags and divide each of them based on urgency
Team member assignment so that every ticket is handled by one person only, secondly if someone comes in the middle gets full context of it.
We send a full report every day based tickets solved, still waiting urgent tickets to.your inbox for a quick check.
It’s still in beta, but I’m curious to know if this is something you’d be interested in trying. I don't want to promote, so let me know if it sounds useful. I am in beta and ready to share to you.
I’d love to hear your thoughts and answer any questions.
Thanks! 😊
I built a support tool for teams that live in Slack and don't want to pay per agent based pricing which goes exponentially high with teams that grows.
I would be happy to know if this solves your problem and if not what would you like to have to switch to syncsupport.
Here's what it actually does:
Email to Slack routing
Live chat widget
Ticket management
AI auto tag and urgency analysis
Canned responses & templates
Analytics
AI monthly digest
CSV export
The pricing model is the part most teams care about:
Who this is for:
Setup is 5 steps: connect Slack, add your domain, create aliases, embed the widget, send a test email. Under 10 minutes total.
Share your reviews, thoughts, if you want to try this you can contact me for discount as well for your team.
SyncSupport is a comprehensive customer support solution designed to integrate seamlessly with your existing workflow, primarily within Slack. It streamlines customer communication by routing support emails directly to designated Slack channels, ensuring no inquiry goes unnoticed. The platform also offers a live chat widget that can be embedded on your website, allowing real-time interaction with visitors, with responses handled directly from Slack.
Built for SMBs, solodevs, soloenterpreneurs small teams who manages customer support from one integrated place, fast, quick and effective.
No need to manage multiple emails, multiple tabs, new filtering strategy, new dashbaord.
SyncSupport eliminates the need to switch between multiple tools, allowing your team to manage all customer interactions from within the familiar environment of Slack or Discord. Setup is designed to be quick and straightforward, enabling you to start providing enhanced customer support in minutes.
Link: https://www.syncsupport.app/
What features will make the product solid and helpful for you? will you pay for it?
SyncSupport is a comprehensive customer support solution designed to integrate seamlessly with your existing workflow, primarily within Slack. It streamlines customer communication by routing support emails directly to designated Slack channels, ensuring no inquiry goes unnoticed. The platform also offers a live chat widget that can be embedded on your website, allowing real-time interaction with visitors, with responses handled directly from Slack.
SyncSupport eliminates the need to switch between multiple tools, allowing your team to manage all customer interactions from within the familiar environment of Slack or Discord. Setup is designed to be quick and straightforward, enabling you to start providing enhanced customer support in minutes.
Today morning I have received few notifications from GSC but I do not know what to do with them.
My project is just 1 week old and I am just starting
As per GSC current stat
1 Total click : 8
2. Total impression : 405
3. Total CTR : 3.4%
4. Average Position : 17.8
Few queries like
external support slack integration, "syncsupport" email management software blog, "syncsupport" vs zendesk
but i am unable to understand what should I do with these queries data. Please help me.
Thanks
I see in the market there are two types of pricing for customer ticket management softwares.
A. Per agent B. Flat based pricing.
I feel for SMBs, soloenterpreneurs per agent cost initially seems to be low but it can grow siginificantly with growth of the teams. Is it the same for you?
Also, they seems to be a bit complex with new dashboard, new software systems, notification system
What are you choosing. I am bit hesitant with zendesk and syncsupport.
Zendesk seems to have per agent pricing and bit complex. On the other hand syncsupport is flat price and simple , managable everything from slack.
Any help would be very helpful .
Last week I launched SyncSupport — a tool that routes support emails directly into Slack so small teams can manage customer tickets without ever leaving Slack and take actions fast, integrate live chat widget and answer from slack. This will be beneficial for solodevs to fix bugs quickly, smbs with small teams, smbs who wants flat price not price/agent.
One week in, no paying customers yet, actively hunting for beta users. But I've already learned more in 7 days than in the months of building.
Here's what I got wrong:
1. I skipped real competitor research and paid for it
I knew who my competitors were — Front, Help Scout, Zendesk. But I didn't go deep enough. I didn't study their Reddit threads, their 1-star reviews, the "why I cancelled" posts. I built what I thought the gap was, not what customers were actually screaming for.
If I'd spent 2 weeks lurking forums before writing a single line of code, I'd have a much sharper positioning today.
Competitor research isn't reading their pricing page. It's reading their angry customers.
2. I spent way too long polishing the UI for an MVP
I genuinely spent weeks getting the UI "right." Animations, spacing, component consistency. For an MVP. For a product with zero users.
Nobody cares how pretty your MVP is. They care if it solves their problem. I should have shipped something functional in half the time and used the saved weeks to talk to customers instead.
Ugly and in users' hands beats beautiful and on your localhost.
3. I chose Resend over AWS SES because I was scared — it cost me $20/month more than it needed to
AWS SES is notoriously cheap (~$0.10/1000 emails). I went with Resend because I wasn't confident setting up SES and Resend had a clean API. Totally understandable at 2am — but now it's a $20/month overhead that compounds.
Not a disaster, but a reminder: don't let lack of confidence push you toward the more expensive option. Resend is great, but I wasn't at scale — I had time to figure out SES.
Uncomfortable ≠ wrong. The scary option is often just the cheaper one.
Where I'm at now:
Would love to hear — what was your biggest mistake in the first week of launching?
Last week I launched SyncSupport — a tool that routes support emails directly into Slack so small teams can manage customer tickets without ever leaving Slack and take actions fast, integrate live chat widget and answer from slack. This will be beneficial for solodevs to fix bugs quickly, smbs with small teams, smbs who wants flat price not price/agent.
One week in, no paying customers yet, actively hunting for beta users. But I've already learned more in 7 days than in the months of building.
Here's what I got wrong:
1. I skipped real competitor research and paid for it
I knew who my competitors were — Front, Help Scout, Zendesk. But I didn't go deep enough. I didn't study their Reddit threads, their 1-star reviews, the "why I cancelled" posts. I built what I thought the gap was, not what customers were actually screaming for.
If I'd spent 2 weeks lurking forums before writing a single line of code, I'd have a much sharper positioning today.
Competitor research isn't reading their pricing page. It's reading their angry customers.
2. I spent way too long polishing the UI for an MVP
I genuinely spent weeks getting the UI "right." Animations, spacing, component consistency. For an MVP. For a product with zero users.
Nobody cares how pretty your MVP is. They care if it solves their problem. I should have shipped something functional in half the time and used the saved weeks to talk to customers instead.
Ugly and in users' hands beats beautiful and on your localhost.
3. I chose Resend over AWS SES because I was scared — it cost me $20/month more than it needed to
AWS SES is notoriously cheap (~$0.10/1000 emails). I went with Resend because I wasn't confident setting up SES and Resend had a clean API. Totally understandable at 2am — but now it's a $20/month overhead that compounds.
Not a disaster, but a reminder: don't let lack of confidence push you toward the more expensive option. Resend is great, but I wasn't at scale — I had time to figure out SES.
Uncomfortable ≠ wrong. The scary option is often just the cheaper one.
Where I'm at now:
Would love to hear — what was your biggest mistake in the first week of launching?