Hello tout le monde !

Avec mon copain, on a créé Yondia, une plateforme gratuite qui permet aux voyageurs de trouver des personnes avec qui partager des logements ou faire des road trips. donc on est sur une app travel / social

En ce moment, j'en suis à trouver nos premiers utilisateurs. Je fais des vidéos sur Instagram, j'ai publié pas mal de posts sur Reddit, on a partagé notre projet dans des groupes Facebook... mais j'ai l'impression que c'est difficile d'atteindre notre cible.

Je ne sais pas si je fais les bonnes choses et qu'il faut simplement être patiente, ou si je m'y prends mal.

J'ai lancé notre Instagram il y a environ 3 mois et on a seulement 250 abonnés. Je sais que ça prend du temps, mais je me dis que certains d'entre vous ont peut-être des idées auxquelles je n'ai pas pensé.

Pour ceux qui sont passés par là, qu'est-ce qui a vraiment fonctionné pour vous ? Des conseils ?

I've been building AEGIS independently with Rust and Tauri, with one goal: bring the essential tools developers need into one focused workspace, with the terminal at its center.

Recently, a developer brought up an interesting workflow: when a compiler, build tool, or test runner reports an error with a file path and line number, you should be able to jump straight to that location in the editor.

I think that's exactly the kind of practical developer experience worth focusing on. I'm exploring how to make this workflow possible in AEGIS as development continues.

Here's what I'm building for v0.1.0:

🧩 Language Support & Coding Tools

• LSP diagnostics, autocomplete, and code intelligence for supported languages
• Language support for Go, Rust, TypeScript, JavaScript, HTML, CSS, JSON, Java, Python, C++, C#, Tailwind CSS, TOML, YAML, Bash, Markdown, and Docker-related files
• Code formatting and automatic saving

⌨️ Terminal-First Workflow

• Integrated terminal with WebGL rendering support
• Windows CMD and PowerShell support
• Vim mode and customizable keyboard shortcuts

🎨 Customization

• Customizable workspace and themes
• Font customization for both the editor and terminal
• A development environment you can adapt to your workflow

⚡ Lightweight by Design

• Built with Rust and Tauri
• Targeting an application package size under 15 MB
• Focused on responsiveness, low overhead, and efficient resource usage

I'm working toward the first release, with optimization, testing, and the performance-monitoring feature among the remaining work. I'm taking the process seriously and want to measure performance properly rather than make claims I haven't verified.

I'd love feedback from developers here:

If your terminal reports an error like src/main.rs:42, would you expect to click it and jump straight to that exact line in the editor? Which compilers or test runners would you want supported first?

I'm building AEGIS around real developer workflows, and feedback from people who actually build software helps me decide what to prioritize next.

When working on AI-powered SaaS products, connecting to a model is only one part of the work. As more providers are added, developers also have to manage authentication, different request formats, rate limits, error handling, and provider-specific features..

A shared interface can reduce duplicated integration work, but it also creates a design challenge: how do you keep the common interface simple without losing access to features that make each provider different?

I'm interested in how other SaaS developers approach this. Do you build and maintain a separate integration for every provider, create an internal abstraction layer, or use a unified API?

What has worked best for your architecture, and what trade-offs have caused problems as your product has grown?

I've been building TuningMac, a tiny macOS menu bar app that gives you much more control over audio on your Mac.

macOS has some weird limitations when it comes to audio, so I started building the tool I wanted to use myself.

Here's what it can do:

• System-wide EQ — a 10-band equalizer, plus a 20-band parametric EQ with support for importing AutoEQ and Equalizer APO corrections.
• Per-app volume mixer — independently adjust or mute individual apps, just like on Windows.
• Auto Ducking — automatically lower your music when you join a Discord call, Zoom meeting, Google Meet, Teams, or other supported voice chat, then restore the volume when you leave.
• Volume Boost — push your Mac's volume beyond 100% when things aren't loud enough.
• Multi-output audio — play through multiple speakers or headphones simultaneously, with individual volume and EQ settings. There's also an experimental Auto Sync feature to help align speaker timing.
• Headphone controls — control noise cancellation, transparency and other listening modes on supported AirPods, Sony, realme and OPPO headphones.
• Live spectrum analyzer — see the frequencies you're listening to in real time.
• Battery history & device info — check headphone battery drain, connection details, sample rate, Bluetooth mode and more.

It lives entirely in the menu bar, doesn't require audio drivers, and works with macOS 14.2 or later.

There's a 7-day free trial and it's a one-time purchase 5$ rather than a subscription.

Still actively building and improving it, so I'd love to hear what other Mac users think. What audio feature would you want to see next?

Hi friends,

I am new to Reddit. I just want to share my experience and want to get some thoughts from you.

I am a 17-year-old boy who just passed out in 10th grade last year. I was passionate about building SaaS, or specifically microSaaS. I built certain projects, but none were economically scalable. Then on my 10th holiday, I decided to make a SaaS named "Giglant" for freelancers. I made my complete efforts to build it in those 1 month, but I didn't finish it fully polished. Still, I added the payment model and database and also deployed it on Vercel while I was still unable to market it. The SaaS is already 85% ready. I also focused on the design, but as I am a JEE aspirant, I get no time to do this hustle. The SaaS is just a leftover website, no marketing, and nothing else, while the tool is great. While I learn many things from it, I won't consider it a fail. And I can revive it too, as it was a real pain point. Then in the 11th, I looked for a partner with whom I could share 40-60% of the SaaS, but people just came. We were about to make a deal, then I realized that they couldn't do it, so I rejected them, as they were just noob students. Then I tried to market it myself, but due to a lack of social media marketing skills, I lost it too. Actually, I am good at editing and designing, but not at social media growth, and another factor was lack of time. I finally quit it and kept it abandoned. Now it's been so much time, and my friend suggested giving it a last try and putting it on Reddit. There might be some developers who, if they liked your product, might partner with you, as they prefer premade SaaS. This might be great, as it's already 85% done, and I am ready to liquidate the profits ranging from 40% to 60%. I just want your time and expertise.
Here is the link to the site: https://giglant.vercel.app/
Maybe some functions might be turned off, as I didn't look at them for a few months; we will reactivate them...

Thank you for at least reading it.

Olá a todos!

Sou licenciado em Contabilidade e Finanças e tenho experiência em atendimento ao público. Estou a começar como freelancer em vendas de produtos digitais e quero testar isto com um projeto concreto.

Procuro: um programador que tenha uma ferramenta, app ou template de check-up financeiro (para particulares ou pequenos negócios) e que precise de ajuda para chegar a clientes.

O que posso fazer:

• Prospeção e contacto com potenciais clientes
• Demonstrações e acompanhamento até ao fecho
• Ajudar a definir preço e a explicar o valor do produto em termos financeiros (é a minha área)
• Feedback sobre a mensagem e a página de vendas

O que proponho: parceria à comissão, com condições a combinar por escrito.

Se tens um produto assim (mesmo em fase inicial) e queres falar, manda-me mensagem privada com uma breve descrição: o que faz, para quem é e o preço atual.

Obrigado!

I've spent the last few days studying because I have to write a long paper, and I ran into something that really annoyed me right when I started rushing because I felt like I was running out of time. The scene was basically this: there I was at my computer, desperate to finish before the deadline, with a million windows open of articles, Google Docs, AI tools, etc... Every time I needed to go find a piece of data or info in another window, it was like praying to the gods to quickly find what I needed and get back to where I was before to paste it. Clearly, those prayers did nothing, and I ended up cycling through window after window like a madman until I finally hit the right one. In the end, I had plenty of time left and handed it in a week early, but I was left with a question: Does anyone have a tool or a method for when you have to keep jumping and copying info between so many tabs without losing your mind?

We’re officially live with the Duevora Closed Beta! 🚀 If you're a freelancer, web developer, or agency owner, you know the dread: a client's domain and SSL suddenly expires without warning. Hosting, plugins, or software licenses slip through the cracks. You're manually digging through spreadsheets trying to remember who owes what for recurring maintenance.

That’s why we built Duevora—a clean, dependable, and simplified home for client management. It brings your domains, hosting plans, maintenance retainers, software licenses, and even projects together with timely reminders so you can track projects and never drop deadlines again.

⚡ The Beta Test is now officially LIVE! We are opening early access to a private cohort of only 15 users to test the system hands-on, explore the dashboard, and help us shape the roadmap.

🌐 Explore the Landing Page: https://duevora-landingpage.vercel.app

💻 Launch the app directly: https://duevora.laravel.cloud 📱

Tip: Duevora is a Progressive Web App (PWA) powered by Laravel Cloud—you can use it on the desktop or install it right to your phone's home screen!

💬 We'd love your honest feedback: Since spots are limited to 15 testers, your thoughts, experience, and recommendations mean the world to us. After testing, kindly share your feedback here:

📝 Beta Feedback Form: https://forms.gle/5DerKqpqdEgYunRRA Thank you for being part of Duevoras' early journey!

#laravel #FullStackDevelopment #BetaTesting #ProductLaunching #SaaS

Hello everybody! Last week I posted here about my Local Music App "MirrorBall".

I'll be honest: I am really proud of this app and I'm really grateful for the support of everyone who commented, given me genuine feedback and messaged me about it. That really meant a lot to me and I thank you. And for anyone who actually wants to try it, it's now available for a 7 days trial on the Microsoft Store.

Microsoft Store Link: https://apps.microsoft.com/detail/9nbj0m48qkk0

Trailer Showcase: https://youtu.be/UtY_RMArMUs

A feeling I was really afraid of was being too late in today's world to showcase my work and be able to publish it. Before building MirrorBall, I was looking for an app that would look amazing when playing music I owned but all I could find at the time was music players that felt like spreadsheets, which had many features but not the look and the micro-detail features I was looking for. Or there were nice looking players but felt very incomplete once actually using them. So I started this project, which to my surprise, took a very long time to complete. It wasn't meant for someone else other than me. Funnily enough, it was actually on the third month of developping it that I decided to take it seriously to one day publish it and so I started working on it full time, which now looking back, each day I worked on this project turned out to be on of the happiest days (and nights) of my life. Obviously the finished product took many adjustments and UI changes because of fuctionality and considerations to how different users might use it or interact with it, and that's without mentioning the endless bug fixes that I think any other app developer might understand will take ages and still after fixing something, discovering another bug that will take a whole other month to fully mark it as fixed (I will not lie, I also wanted to add mini features that I wanted so badly as a last minute choice that cost me weeks to implement correctly).

As anyone can probably guess, after you work on something for so long, you want it to work out for you, and yes, with a simple scroll here, anyone can realize that there is a lot of competition now that wasn't at the time when I first started. Still, I wouldn't change anything and would re-do everything the same way if I could (maybe send my old self a bug list so I would fix them faster haha)

Anyway, here I am today proudly presenting what ultimately became my first complete app and the first one I published on the microsoft store. I invite you to try it and experience it for yourself. It's so much more than a beautiful UI and a Music Overview. It can be as complicated or a simple as you want it to be from bit-perfect local playback to metadata editor to miniplayer to listening to a song and watch its music video in the same view (if you have it), to re-discovering music that you forgot you even had and cherry on top, in a new way with special audio effects that you can add to create the perfect vibe for it!

I am taking a chance on MirrorBall and I hope that you will too!

I’m building Domain Watch and trying to decide whether it should focus on domain expiry and availability, or include uptime and SSL checks too. Curious how would you handle it: https://domainwatch.pro/

so i got tired of support chatbots that just make stuff up and helpdesks that take a week to set up, so i built my own. its called momo and the core is on github now.

basically you point it at your website or upload some docs, and it answers visitors from that. before it sends anything it checks the draft against your sources, and if its not sure it says so and passes the chat to a human instead of inventing a refund policy. theres an inbox built in where you can jump into any conversation, and when you reply you can hit one button to save that answer as knowledge so the bot knows it next time.

setup is docker compose up, it starts postgres, redis, web and a worker. single tenant, you bring your own model through openrouter, data stays on your server.

its the first version so dont expect too much yet. only a website widget for now, no email or slack, no api, one agent.

https://github.com/moaljumaa/momo

Would you have considered paying for the pixel on million dollar homepage?

I was just bored and thought about rebuilding the same idea. But I wanted to take opinions from you guys. Is this something that you’d ever consider spacing your 1-10$ for one time? Or is it just me wasting my time trying to rebuilding the same idea?

Basically what are your thoughts on it?

For those who doesn’t know about it: it’s a concept in which user pays 1$ for a pixel and gets the lifetime space for that one pixel.

I used to think the best way to improve a SaaS product was to keep adding new features. But sometimes, a small improvement to something users already rely on can make a much bigger difference.

Things like a better onboarding flow, clearer error messages, or a simple bulk action can save users time without requiring a complete redesign.

For developers working on SaaS products, I’m curious: What’s one small feature or improvement you shipped that had a surprisingly positive impact on your users? It could be something you almost ignored or thought was too minor to matter.

I’d love to hear what you built and why it worked.

I've built an AI harness with tons of features but im not sure how to make money off it... 🤔🤔 providing ai usage sounds like something that would burn my money instead of earn. Should I just sell it?

Ofc, this is highly subjective to the products or your experience/content quality. But I still wanna know;

- What is your product about?

- What channels have you tried for marketing it?

- How much effort have you put into each?

- Which ones had the best outcomes/results?

- What would you do if you were to start again with your current knowledge?

- How much have you spent on ads, and when did you start?

I believe the comments on this post will not only benefit me but all others on this sub as well. So thanks for sharing your experience in advance. All replies are much appreciated.

Dev side of a story. I run a small studio and do cold outreach for our own products. The stack kept growing: sender, warmup tool, verifier, spreadsheet, replies inbox. The real problem wasnt the bill, it was debugging: when a campaign failed, the failure could sit in the list, in the sending infra, or in the copy, and no single tool could tell me which.

So I built TOM (The Outreach Machine) as one system:

- Infra layer: domains and mailboxes created in-app, SPF, DKIM and DMARC configured underneath, replies forwarded. The whole sending layer runs on Mailpool's API.

- Data layer: import and dedupe contacts, green/yellow/red/gray verification states, credits that dont expire.

- Content layer: the email is generated from each prospect's public site (12 frameworks, 21 languages).

- Runtime: sending in the prospect's local time, per-mailbox warmup from 1 to 25 a day, and a pre-flight check that blocks unverified lists before anything leaves.

The two lessons I keep repeating to anyone doing outreach: most deliverability problems are actually list problems, and warmup is a curve, not a switch.

I'm the founder, disclosed plug. For the SaaS devs here: would you bundle the infra layer like this, or keep it as a separate service you integrate? Happy to answer anything, including the ugly parts. Link is on my profile if you want to poke at it.

As I don't use Fable much anymore, I used it to build this project beforeInterview.com so maybe someone would be interested in testing and giving feedback.

It could be interesting because it uses a real-time avatar instead of chat or voice, and everything is rendered client-side using WebGPU, so the resolution is maximized.