Me and my co-founder took a few days off work.

Not for a vacation.

But for a 4-day marathon to try and finish our first SaaS.

Any tips to survive the grind?

Let me introduce you to Groop, a product I've built out of pure frustration. Every time I wanted to meet with friends or plan a holiday it was a hassle of constant back-and-forth messaging to check who was available when.

That's why I created Groop, a simple and free solution. It works like this

• Go to groop.cc
• Create a Groop (Eg. summer holiday 2025)
• Send the link to friends
• Everyone can select available dates on a calendar
• The dates when everyone is available are highlighted in green

It doesn't get more simpler than this. No account creation required. No more back-and-forth-messaging.

Check it out: groop.cc

Hey Huzzlers,

I have something very useful to share with you. It's what I just realised Yesterday And sharing it with you right now.

I was deep into building SnapStats.

Every new feature felt like progress like...

• This will give users more value.
• This will make it better.

Then I went deep—content effectiveness scores, referrer intelligence, lifecycles, dashboards.

It looked clean, worked well, but here’s the truth:

I didn’t even know what feature actually mattered to the user.

I was trapped in a cycle of building stuff because I thought it was cool, not because it solved a problem.

So I asked myself the real question:

If I had to pay for this product, would I?

And honestly, I couldn’t answer yes.

Because I built it thinking, “This would be cool” instead of, This solves a problem.

That spiraled into:

• Did I just stack features with no real reason?
• Am I solving anything—or just building what I want to see?

That’s when the clarity hit.

Users come for solutions, not features. If you love money? 👉 Solve one problem, solve it well.

I paused.

No dashboards. No code. Just me vs reality.

I sat down and asked myself:

• Who’s this really for?
• What’s the core problem they’re facing?
• Why would someone pay today?

And the biggest truth slapped me:

More features = more confusion.

Clarity? Gone. Value? Lost in the noise.

So I started cutting.

Stripping everything down to the one thing worth paying for. The real, core value.

I started focusing on solving a specific pain (let it be the very small one). And now, the vision feels clearer and way more focused.

So what you guys can learn from it?

When you’re stuck in the feature spiral, just ship your product with that one pain-relieving feature.

Forget about the extra features for now. Keep your long list of "cool features" saved somewhere, but launch with the one thing that’s actually worth paying for.

Here’s why:

When users come to your product, they’ll tell you what they want. You don’t need to guess or overbuild. Let me clarify....

Once you launch, gather feedback.

What are users asking for? What features do they actually care about?

Then look at your saved list of features and see if any of them align with what users are requesting. If so, you’re on the right track. If not, rethink. Don’t add unnecessary complexity.

The key here is simplicity and real-world validation.

• Ship your product early.
• Iterate based on real feedback.
• Don’t try to be everything to everyone right out of the gate.

(I only realized this yesterday, so trust me, I’ve been there!)

Final insight:

The world doesn’t need more features. It needs simple, effective solutions that solve real problems. Focus on that, and let your users tell you what comes next.

They’ll tell you what they need—you just need to listen. Example ... Huzzler itself.

The project

I build language learning applications, because I love learning languages.

So I built a game called Grake, which is inspired from the classic game Snake, except you grow the snake by capturing the words in the right order.

This is playful way to learn grammar, vocabulary, and syntax in foreign languages.

How I did it

1. Used Ahrefs to find common expressions that people search for such as :

How to say in spanish.

this resulted in 33,691 keywords in the USA alone.

2. I filtered for low KD and high SV.

3. Then created pages that exemplify the word or phrase that match that keyword in Grake.

As a result I created pages whose title, description, and keywords in the metadata contained said keywords.

After 1 month, I successfully ranked for 140 keywords.

Although only 1 of them is top 10, I feel optimistic about my strategy of generating traffic, while I continue marketing my language learning application.

Here's the video, where I show the proof and how I did it.

I've come across this website that gives you a decent amount of marketing blocks to use. Pair this with some good sales copy and you should be good to go.

https://tailark.com

Hi all,

I’m a college student trying to build my first SaaS product. I don’t have a technical background, and I can’t afford to hire developers, so I’m exploring free and low-code/no-code tools (what some people call “vibe coding”?).

Right now, I’m in the learning and planning stage. I don’t have a finished idea yet, just a strong interest in creating something real and figuring things out as I go. I’d love to hear from anyone who’s:

1. Built a SaaS without a tech background

2. Used free tools or no-code platforms to get started

3. Is currently working on a similar project

Any tips, recommended tools, lessons learned, or just general advice would mean a lot. I’m not trying to promote anything – just here to learn and connect.

Thanks in advance!

Yesterday I made a post on how to use Gemini + Gamma to make a website in minutes.

Honestly, it's an amazing combination.

But, did you know that GenSpark, can do a similar job for you without using any other tools ?

This was my prompt

I am creating a video on the meaning of colors across cultures.
return a well formatted report with a table on the meaning of colors across all the major cultures, such as Western, Chinese, Indian, West African, Native American, etc
make it into a presentation.

This is what it returned.

Now I can design my course on color design much faster.

Here's the YT Tutorial.

Hello everyone. Here are some tips on how to get your first 500 users for your SaaS.

Getting your first 500 users takes work, but it's possible if you follow a plan. If I were starting a new software business today, here are the 5 steps I'd take:

1. Find a real problem people have. Think about problems you deal with yourself or problems in areas you know well.
2. Talk to at least 10 people who have this problem. Ask them questions (like in surveys or calls): How do they handle it now? How much does it bother them? Would they pay for a solution?
3. Build a basic version of your product (an MVP) that solves the main problem. Don't add extra features yet, just make sure it works.
4. Let the people you talked to use your basic product for free. Ask them what they think. Use their feedback to improve it. Then, tell people about it in online groups where potential users hang out to get your first 100 users.
5. Improve the product based on what those first users say. Then, launch it on Product Hunt to get even more users.

Hopefully this helps some of you

Follow these steps:

1. Go to indiehackers(dot)com/products

2. Click on submit update

3. You will be redirected to your product (if not added, you need to submit your product first)

4. Write a post/update about your product

5. Once published, your update will be visible on the Build Board

Notes:

• Try to add updates on weekdays to get more benefits.
• Try to add new product updates at least twice a month.

Hey everyone!

We are very excited to announce that you can now install Huzzler on your mobile device and receive push notifications. We have opted to use a PWA instead of a native app as we plan on shipping as many features in the coming weeks (problem / solution directory, accountability, marketing guides..).

To install the app: Simply visit the Huzzler homepage on a mobile device. A popup will appear with instructions on how to install the app. Cheers and let me know if you have any feedback 😁

Thanks!

Building the backend for your application is a critical decision that can significantly impact development speed, scalability, and long-term maintainability. Two popular approaches are using a Backend-as-a-Service (BaaS) like Supabase or building a traditional backend with frameworks like NestJS and databases like PostgreSQL. Both have their strengths and weaknesses, and the "best" choice depends heavily on your project's specific needs. (TLDR at the bottom)

Backend-as-a-Service (BaaS) - Supabase

Supabase is an open-source alternative to Firebase that provides a fully managed backend out of the box. It’s designed to help developers launch products quickly without having to set up and maintain their own backend stack.

What Supabase offers:

• PostgreSQL database with real-time subscriptions
• Authentication with social logins and row-level security (RLS)
• File storage with security rules
• Serverless edge functions for custom logic
• WebSocket-based real time updates
• Frontend-friendly SDKs for easy integration with frameworks like React, Angular, Vue, etc.

Benefits:

• Fast development: Great for building MVPs quickly.
• Low barrier to entry: Minimal backend expertise needed.
• Scalable (managed): Supabase handles infrastructure so you can focus on your features.
• Cost-effective for early-stage apps: Generous free tier and simple pricing.
• Open source: You can self-host later if needed.
• Smooth frontend integration: Built with frontend devs in mind and now vibe coders.

Disadvantages:

• Less customization: Limited control over the backend stack.
• Vendor lock-in: Migrating away can get tricky if you rely on Supabase-specific features.
• Scaling costs: Can get expensive at higher usage levels.
• Advanced feature learning curve: Features like RLS or edge functions take time to master.

Traditional Backend – NestJS & PostgreSQL

Going the traditional backend route means setting up and managing your own server-side infrastructure. With a framework like NestJS and a relational database like PostgreSQL, you’re in full control of how your backend operates. This approach is ideal for developers who want maximum flexibility, deep customization, and long-term scalability.

What it typically involves:

• Handling authentication, business logic, and API routes manually
• Deploying on your infrastructure (e.g., VPS, cloud platforms)
• Managing DevOps, monitoring, and scaling yourself

Benefits:

• Full control: Customize every aspect of your backend.
• Highly flexible: Integrate any library or service that fits your use case.
• No vendor lock-in: You own your entire codebase and database.
• Optimized performance: You can fine-tune performance and costs to your specific needs.

Disadvantages:

• Slower initial dev time: You’ll spend more time on setup and configuration.
• Higher barrier to entry: Requires backend knowledge and server-side experience.
• More upfront costs: Hosting, monitoring, and backups can add up.
• Boilerplate code: Expect to write more code for common features like auth, validation, etc.

When to Choose Which:

Choose Supabase (or another BaaS) if:

• You need to launch fast and iterate quickly.
• You or your team have limited backend experience.
• You want to focus mostly on the frontend.
• Your app has standard backend needs (auth, DB, storage).

Choose NestJS & PostgreSQL (or a traditional backend) if:

• You have complex or custom backend requirements.
• You want to avoid vendor lock-in at all costs.
• You have backend skills (or a team that does).
• Long-term cost optimization and full control are key to your strategy.
• You need to integrate with specialized tools, services, or workflows.

There's no universally "better" option. Supabase and NestJS/PostgreSQL represent different approaches to backend development, each with its own set of trade-offs. Ultimately, the right choice is the one that empowers you to build and scale your application effectively.

___________________________________________________________________________

TLDR:

BaaS (like Supabase): Quick to start, easy for frontend-focused teams, handles backend basics (DB, auth, storage) and scaling, but less customization and potential vendor lock-in. Good for fast MVPs.

Traditional (like NestJS & PostgreSQL): Full control and customization, no vendor lock-in, optimized for specific needs, but slower initial setup and requires more backend expertise. Better for complex, long-term projects. Choose based on speed vs. control.

I looked at starter kit made by WebDevCody and saw this rate limiter implementation.

Very easy to use and does the job, suitable for when you have only one instance. You would need something like Redis to scale this up for multiple instances.

You can check it out here -> https://github.com/webdevcody/wdc-saas-starter-kit/blob/main/src/lib/limiter.ts

I was researching on the meaning of color across cultures, as part of a video I am working on. So, I need a research tool.

Now, I need to create a presentation or a website in minutes.

Can I do that ?

Yes.

There's a 2 step formula that I found:

1. Use a Deep Research Tool (Gemini, ChatGPT, etc) -- this is how I conducted my research.
2. Use a text to presentation maker, namely Gamma.App.

Here's the final output by gamma. Just crazy.

Here's the YT tutorial: https://youtu.be/Sz2jNt2KHCw

Something I've noticed is how often you can stumble upon potential SaaS ideas just by reading through Reddit.

If you browse subreddits where entrepreneurs, developers, or other professionals hang out, you'll frequently see people talking about problems they face or wishing for a specific tool to make their work easier. They might complain about a tedious task or ask if anyone knows software that does a particular thing.

When you see posts like that, it's often a sign that there's an unmet need. You could create something that other people will actually want. Maybe the existing tools aren't quite right, are too expensive, or people just don't know about them because of poor marketing.

What I've found helpful is keeping an eye out for these kinds of psots. If you see multiple posts over time where people describe similar frustrations or wish for the same type of tool, that could be a strong signal for a good product idea. It shows there's a real need people might be willing to pay to solve.

Just a thought I wanted to share. Has anyone else noticed the same?

You may now bookmark posts on Huzzler! You can find your bookmarks in the top right corner when pressing you profile picture 🥳

I've used photoshop and Photopea (free web photoshop alternative) casually for the past 10 years but Photopea has recently been buggy for me to use.

Has anyone on here tried affinity photo 2? It's a one-time payment and is supposed to be very comparable with photoshop. I mainly need basic editing features such as layer styles. and be able to open and save images as .psd files.

I also tried Gimp but I really dislike the UI.

So if anyone tried it, feel free to let me know, anything is appreciated! Thanks guys

If you’ve recently launched (or are planning to launch) a product, service, or offer — I’d love to hear:

What’s been the hardest part?

• Design
• Messaging
• Getting conversions
• ...

I’m digging into how founders experience the website process — and your insights would mean a lot. 

Reach thousands of active founders looking for tools to solve their problems. Our Featured Product placement guarantees premium visibility with 7,458 weekly impressions for post ads (like you are reading right now).

Get direct access to your perfect target audience - people actively building, launching, and growing startups who are ready to invest in solutions like yours. Limited weekly slots available.

Reserve yours now at huzzler.so/advertise

OpenRouter.AI is an LLM and multimodal model inference management service.

You issue an API key once.

Then you choose which model you want to use.

Set your prompt.

Ready to go.

You can also use it for free (up to 1k requests / day)

Here's a short demo.

A month ago, I had zero clue about tech. GitHub? Never touched it. Deploying an app? Sounded like something only real devs do. It felt like building your own app was reserved for ‘real’ developers — not someone like me who didn’t even know where to start.

But I had this idea — and instead of waiting until I “learn how to code,” I just went for it. I stumbled into the world of vibe coding, and it completely changed the game for me.

Three days later, I launched my very first app:

👉 BoomHabits.com — a simple habit tracker to help people stay focused, build routines, and feel proud of their progress.

And here’s the crazy part: three days after going live, 200 people signed up, and BoomHabits got 80 upvotes as Product of the Day on Fazier.com (we even hit #2 for a while!).

I know for a lot of you — devs and folks who’ve been in this world way longer — this might seem small, maybe even kinda funny. But for someone who’s never written a single line of code… this is huge!

Just wanted to share this little win — the vibe coding is just getting started for me. Maybe it’ll inspire someone else to take their first step too.

From the image below, it seems vibe coders have a long way to go before they can actually make safe and secure products.

"Even products from top devs get hacked too," yes, but they usually do know how to go around it.

The best way to prevent getting hacked include:

1. Familiarising yourself with the workings of your framework, programming language, libraries, etc.

2. Always use HTTPS everywhere!

3. Always hash passwords!

4. Use env. variables for api keys, passwords, client IDs.

5. Make sure you run your logs, so you can use them for forensic investigations if a security breach happens.

6. Use prompts such as 'Undertake a full review of any risks associated with exposing personal identifiable information to a malicious actor. Investigate, explain, resolve.' while vibe coding.

Please feel free to add any other pieces of advice.

Hello guys. We talk about tech stacks all the time, always using the latest shiny new javascript framework. But I'm wondering. What tech stack are you actually the most productive in? Can be different from what you use now, but what can you code the fastest with?

I just launched my second iOS app called FastZen – Fasting Tracker 🕒

It’s a clean, focused intermittent fasting app designed for people who want to stay consistent with their fasting routines without distractions or clutter.

I built it for anyone looking for a smooth, minimal experience—start a fast, get smart reminders, and stay on track with a clear overview of your progress.

Would love to get some feedback on the UI and the overall user experience 🙌

https://apps.apple.com/us/app/fastzen-intermittent-fasting/id6744087602

Hey everyone! Today I've added embeddable badges. All products listed on Huzzler have received an embeddable badge, feel free to add this badge to your website 😁

You can now also win gold, silver and bronze badges in the launch arena.

Hey everyone 👋 For those interested, we've added new advertising options ranging from 1,659 up to 7,458 weekly impressions.

Only until April 30th , we're doing a sale were you get 25 bonus ad credits per 100 credits purchased️

Advertising options: huzzler.so/advertise/options-pricing

Upcoming features for Huzzler

Now that the development on the advertising system is done, we're focusing on making Huzzler the best platform for founders. Here is a list of a couple of the planned features we have:

• Automatically add your product to "alternative to" so people can find your products through SEO
• Be able to save / bookmark valuable posts in folders
• Accountability system where you can define goals and celebrate milestones with the community weekly (you will be held accountable by the community) 😉
• A problem/solution directory where users can submit real world problems they have. This will provide Huzzler users with a list of already validated product ideas. You'll also be able to notify the user who posted the problem when your app is ready, that way you already have a paying customer ready.
• Gamification: have a level and xp. Increase your level by contributing in the community
• Referral system: gain advertising credits by referring people to Huzzler
• OAuth, login with Google
• Embeddable badges for the launch Arena
• Be able to link a product with a showcase
• Better filtering / sorting in product pages (filter by category, sort by date,..)
• Coming soon tab: all projects that are soon to be relelased
• Previous launch arena winners pages
• .... and many more features

Let me know if you'd like to see other features as well 😁

Thanks for reading guys!

Hi there,

I need some recommendations and guidance. I'm working on a personal project that I want to turn into a SAAS. I have no experience at building a SAAS app and I want to understand the steps to do so. Right now the backend is built in Python and I was thinking of Flask for the front end. Where should I start to take it to the next level? Thank in advance

This is the 3rd part of the Vibe Coding tutorial series. If you missed the first two, you can check them out here:

• First Post - Vibe Coding: How to Build Anything Using Simple English Prompts
• Second Post - Cursor Rules Guide

This is a guide to connect GitHub with Cursor using MCP (Minimal Command Protocol). MCP allows you to interact with GitHub directly from Cursor. Once connected, you can use prompts like:

• Create a new repo with the current app you’re building
• Push your code to GitHub with a single command
• Search for repositories, pull requests, or issues
• Edit files or manage issues without needing to type Git commands

Just give Cursor a prompt, and MCP handles the rest, making your GitHub workflow effortless!

Step 1: Generate a GitHub Token

Visit this link: Generate Token

• Name your token
• Set the expiration date (I usually set it to "30 Days")
• Under Repository Access, choose “All repositories” or select specific ones as needed

Step 2: Set Basic Repository Permissions

Give read and write access to the following scopes:

• Actions
• Administration
• Commit statuses
• Contents
• Issues

Scroll down and click Generate token, then copy the token.

Step 3: Connect via Smithery

Go to: Smithery GitHub Server Setup

• Log in with GitHub
• Select the IDE you're using (Cursor, Windsurf, etc.)
• Paste your GitHub token under githubPersonalAccessToken
• Click Save and Connect

Note: Smithery is open-source, but be cautious when giving access to your personal account.

Step 4: Add GitHub MCP to Cursor

Once you've clicked Save and Connect on Smithery, you'll get two options: npm or JSON. I recommend choosing JSON.

1. Click on JSON, then copy the full configuration.
2. Open Cursor
3. Go to Settings → MCP Servers → Add New Global MCP Server
4. Paste the JSON you copied
5. Hit Save

Step 5: (Optional) Enable YOLO Mode

Cursor → Settings → Features:

• Enable YOLO Mode to let the agent run tools without asking for confirmation each time
• Enable Delete File Protection so files aren’t deleted without warning

With this setup, Cursor can:

• Create/Edit and upload repositories
• Search repositories, issues, and users
• Push code directly to GitHub
• Automate workflows

Coming up next:

A full guide on installing browser-tools, no more screenshots or back-and-forth debugging. With this, Cursor can directly interact with your browser.

You’ll be able to open Inspect Element (F12), click on any section of your site, and then just go to Cursor and ask: "How can I improve this?" or "What’s wrong here?"

It can read the DOM, check console errors, network logs, and even take screenshots.

Three years back, I didn’t know how to build websites. I wasn’t a developer. I wasn’t a marketer.

Just a middle-class guy trying to figure out how to make a living.

All I knew was—I could write. So I started there.

Blogging was my starting point.

No paid courses. No YouTube gurus. Just me, observing, writing, and learning by doing.

I wasn’t aiming to be perfect. I was aiming to be useful.

Fast forward to March 2024—I launched ai-q.in. A blog focused on AI tools. (It wasn’t my first blog either—there were a few failed ones before that. Each one taught me what not to do.)

And here’s how I made it work:

1. I Skipped the Fluff. I Studied Competitors.

I didn’t guess what to write. I reverse-engineered the top 10 results on Google for every keyword I picked.

I checked:

• What they were doing well
• What they were missing
• How I could write better by actually connecting with the reader

Most of those top sites were big—but they weren’t personal. They didn’t speak to real user problems.

So I did. I made sure every paragraph hit a pain point.

2. I Wrote to Solve, Not to Impress

A lot of content is written to sound smart. I didn’t care about that.

I focused on connecting with the user. I wrote how I talk. I hit pain points. I skipped the fluff.

And it worked. Google noticed. So did readers.

Because people share what makes them feel understood—not just what ranks.

3. I Delivered What Others Didn't

Most of those top 10 blogs? Big companies. Polished. Optimized.

But also—vague, robotic, and filled with filler.

I went the opposite direction:

Detailed guides, Clear breakdowns, Stuff they actually needed but couldn’t find anywhere else.

I covered what those 10 sites skipped. I didn’t just rewrite—I added depth, insights, and clarity.

That’s what ranked.

The Result?

Launched on Feb 4th, 2024 → Hit 75K+ traffic in 40 days.

No backlinks. No hacks. No ads.

Just real content, written for real people.

In the next 2 months, platforms like Viggle, FlexClip, Vidnoz, GetIMG, and many more reached out.

I reviewed their tools, made solid income from it, and grew even faster.

What Indie Makers Can Take From This

If you’ve got a product, idea, or even just a landing page—start writing content around it.

Answer what your users are Googling. Show up with real value.

Keep doing that, and traffic will come.

• You don’t need a marketing degree.
• You don’t need an ad budget.
• You need to be useful, consistent, and smarter than the platforms you’re competing with.

Here’s what you can start doing today:

• Pick one feature or tool from your product and write a real guide around it
• Research, analyze, and write better than everyone else. It’s doable.
• Focus on helping one reader, not cracking SEO.

SEO isn't dead. Bad content is.

PS: I’ve moved on to building products now (another story for another day). But content? It’s still the reason any of this was possible.

When launching or developing a SaaS product, selecting the correct pricing approach may make or break your business's success. Each freemium, free trial, subscription, and lifetime deal model has advantages and disadvantages, and the optimal option often depends by your product, audience, and goals.

Here is a simple breakdown of each model:

The Subscription Model: The Old Reliable

With subscriptions, users pay monthly, quarterly, or yearly to keep using the product. It’s super common and for good reason.

For users:

• ✅ Lower upfront cost
• ✅ Ongoing support and updates
• ✅ Can scale up or down with different pricing tiers
• ❌ Might end up paying more over time
• ❌ Another monthly fee to track
• ❌ Can feel locked into the service

For businesses:

• ✅ Predictable, recurring income
• ✅ Builds long-term customer relationships
• ✅ Easier to forecast growth and cash flow
• ❌ You’ve got to keep delivering value to reduce churn
• ❌ Higher upfront investment in building and maintaining the product

Lifetime Deal: Quick Cash, Long-Term Trade-Off

This one’s simple users pay once and get access forever. No more bills. Lifetime deals are especially popular for early-stage products looking to raise quick funds or attract early adopters.

For users:

• ✅ One-time payment = peace of mind
• ✅ No ongoing fees
• ❌ Might not get future updates or support
• ❌ If the product doesn’t last, they lose out

For businesses:

• ✅ Brings in fast cash
• ✅ Attracts early users who can give feedback
• ❌ No recurring revenue = limited growth
• ❌ Long-term support for users who never pay again
• ❌ Can hurt perceived value of the product

Freemium: Free Forever (Until You Want More)

Freemium gives users basic features for free, with the option to pay for more advanced stuff.

For users:

• ✅ Easy to try without commitment
• ✅ Can stay on the free plan if needs are simple
• ❌ Limited features
• ❌ Might have ads or nudges to upgrade

For businesses:

• ✅ Low friction for sign-ups
• ✅ Potential for word-of-mouth growth
• ❌ Feedback from a wide range of users
• ❌ Can get expensive to support all the free users
• ❌ Usually low conversion rates unless the upgrade is compelling

Free Trial: Try Before You Buy (For Real)

Free trials give users full access for a short time think 7, 14, or 30 days so they can explore everything before paying.

For users:

• ✅ Full access with no risk
• ✅ Helps decide if it’s a good fit
• ❌ Limited time to evaluate everything
• ❌ Lose access if they don’t upgrade

For businesses:

• ✅ Shows off your product’s value
• ✅ Can lead to higher conversion rates than freemium
• ❌ Need solid onboarding to help users see the value fast
• ❌ Might attract people who just want a quick free ride

So there you have it: an overview on SaaS pricing. There is no single "right" method to do it, it all relies on your product, who you want to target, and what your objectives are. You could even combine a few of these! The main thing is to consider what makes the most sense for your business and to keep changing as you learn what works best.

Hey everyone, after getting exactly no feedback about my idea on reddit i accidentally stumbled about this community and want to give it a try.

I've have a simple idea for such some time now build landing pages and some simple working mocks.

A flexible web-based dashboard. It's a simple, tile-based web app where each tile can launch something – a YouTube video, a Spotify playlist, a website, or even a call via WebRTC. 

The idea started as a media hub for children – something safe, easy to use, and distraction-free. Imagine a kid tapping a big button to call grandma (via WebRTC), or launching their favorite bedtime story video without needing to search or type anything and the media starts playing inside my app.

But the concept seems scalable and highly adaptable.It could be useful for:

- Kids

- Seniors

- People with disabilities

- Shortcut dashboards for families or teams

I’m now at a crossroads:

What problem should this actually solve to dig deeper into one niche ?

Is the kids use case already too saturated with existing tools (e.g. Fire tablets)?

Would this be more useful for assisted access?

Should it evolve into something totally different?

I’d love to hear your thoughts on possible directions, pain points this could solve, or even your gut feeling about the idea.

Thanks so much for reading and please be honest with me. if u think this is total bullshit or useless I am fine with it too. what I don't want is to waste time to build a product no one wants to use ;)

Some of you requested functionality to be able to comment on product pages, so we've added it to Huzzler 🥳

In addition to the product comments, we've also improved profile pages. Your products are now directly visible on your profile without having to click on the 'products' tab.

It's now also possible to delete your posts or products.

Thanks for the feedback everyone! Keep building 💪

Let me introduce you to Groop, a product I've built out of pure frustration. Every time I wanted to meet with friends or plan a holiday it was a hassle of constant back-and-forth messaging to check who was available when.

That's why I created Groop, a simple and free solution. It works like this

• Go to groop.cc
• Create a Groop (Eg. summer holiday 2025)
• Send the link to friends
• Everyone can select available dates on a calendar
• The dates when everyone is available are highlighted in green

It doesn't get more simpler than this. No account creation required. No more back-and-forth-messaging.

Check it out: groop.cc

Hey Everyone,

I'm new to the platform. Came across the a post on Reddit featuring this site so figured I'd hang out here. What are your thoughts on the idea?

Right now I'm working an MVP for the for the app:

• This will be a platform that aims to support and connect local communities. The platform will give users the ability to search through listings locally(Exchange, Gifting, Buying/Selling).
• Sellers will be able to open "Storefronts".
• Social events, groups and feed.
• Ability to coordinate courier services between users who "volunteer" and users who are requesting services.
• Rating/trust system for users who are active on the platform.

I'm looking to capture users who are:

• Fed up with current social media or are using Discord/Whatsapp and other messaging apps
• Local CSAs
• Already have a storefront on Etsy, Ebay, etc.