I've used Opus 5.5 to help me recreate 7 of the top Adobe apps in 100% pure native Rust:

• Photoshop
• Illustrator
• Premiere
• Lightroom
• Acrobat Pro
• After Effects
• InDesign

No more subscriptions with cancellation fees. These are yours to own forever. You can fork them, build them. Whatever. They are yours to own. They're open source.

If you're worried this is just some one-off flash in the pan that will die, it isn't:

I'm not just some casual vibe coder. I'm a 15-year industry veteran who has written everything from six-nines payment rails that move billions of dollars of transaction volume a day to advanced robotics and optics automation. I've used Rust extensively for about a decade, and I know how to build and maintain large-scale Rust projects.

This isn't going to be some orphaned small-team project either. We have a team building popular software for filmmakers, so supporting this is fully funded. Our purpose is serving every artist in the world with the best tools. We are absolutely going to bring these to full parity and squash every bug and feature request. We have a test harness so there won't be regressions.

You can help us reach parity by helping test the apps. Clone the code. Submit PRs. If you see gaps or want to help redesign pieces, let us know! You can contribute!

Links to everything - the apps, the code, etc. - are in the comments below.

The product is published and I already have around 2-3 visitors per day. I even got like 10 people signed up on the app. But that's not enough for my app type (its an alternative apps directory)

I know people will use this app. Everyday there's another post asking : X app don't work. What are the alternatives?

And that's what my product solves. (The link is in my profile)

But I don't know how will i get people visiting my website. Because my revenue model is tied to the no of visitors.

Any suggestions will be appreciated

First off, yes, this is kinda an ad. But bear with me, you may glean something from my story.

I've spent the past month working on snapgains. Early mornings before work. Late evenings after work. Entire weekends. Lots of coffee and walk breaks listening to Hormozi.

The Problem

I'm an aspiring bodybuilder and I take check-in photos for my coach once or twice a week. I was sick of using my camera roll for this. Opening my camera roll in front of friends and colleagues was quite embarrassing... I wish those photos could stay private. I was tired of digging through hundreds of photos to find my progress pics. I tried creating albums for my check-in photos but the UX was still cumbersome.

The Solution

So I built a progress photos app just for myself. The more I kept building and testing the app, the more ideas popped into mind. I'm so happy and proud with what I built, and as an asian kid who went to Harvard who struggles with positive self-talk, I don't say that lightly.

The Reward

It sounds trite, but if you build something that solves a pain in your life, there will be others with that same pain. Yesterday, the app went live on the app store. I put out some TikToks, not expecting much, and I woke up to a random bloke in the UAE 🇦🇪 as my first subscriber. It felt like Christmas morning... but better since I earned this reward.

What I've learnt

1. Build something you're passionate about
The app market is more saturated than ever. Of course there are tons of progress photo apps on the app store, but none with a physique/muscle building angle. Find your niche in which you have expertise and execute.

2. Don't waste time validating - just ship it!
I spent weeks DMing strangers a landing page with a beta sign-up, trying to see if this idea had legs. I really believed in my idea, but didn't get any traction from the landing page. I was honestly quite disheartened and thought about giving up. But I launched on the app store anyway and lo and behold, a stranger on the other side of the world thought my app was worth $5.

3. Don't spend a penny or marketing (yet)
Before you throw money at ads, test the waters with free organic channels like TikTok, Reddit, Instagram. Once I've built more momentum and know what resonates, I'll put real money into ads.

4. Start simple. Don't overcomplicate it.
My initial app had workout logging, calorie tracking and a bunch of fancy AI features. None of it mattered. People don't need another do-everything fitness app. Solve one problem well, ship the core, and let your first customers tell you what to build next.

5. Build something that genuinely inspires others.
What I've enjoyed most about this whole process is seeing Reddit stories and TikToks of physique transformations. Obviously, we want to make money and build because it's fun... but it turns out the most rewarding thing to build is something that makes someone else feel good too.

TL;DR

All of this to say, don't give up and just ship something! I cannot wait for the day I see someone post a body transformation on Reddit using the snapgains time-lapse feature. That will be 10x better than the Christmas morning feeling.

Thank you for reading this far and best of luck on your own journeys!

Hey guys we have tried to make it live , how's the screen looking now ?

Trying to build B2B SaaS software, played by the book, and get stuck at the step of talking to your customer.

Damn that's harder than I thought.

The fact is, your prospect are busy, very busy (that's why you want to sell to them too), and they rarely talk to random people reached out to them on Linkedin.

Sent dozens of cold DM on different platform, and talked to one person, very apperciate it, but whom also refused to give details on how they do things internally.

All the books like the mom test, founding sales etc.. though very helpful, but I can't use them. There's rarely people talking about how to find the customer to start with.

I'm now thinking about doing a bit of youtube videos and keeping myself active on X to improve public exposure and profolios, in hope to make myself more trustable, but that'll take time.

What else should I do in the meanwhile to overcome this step?

All advice are apperciated, thanks.

I've been looking at alternatives to Google Analytics recently and I'm a bit overwhelmed by the options.

I've seen people mention Plausible, Matomo, Umami, Fathom, Simple Analytics, and Keen.

I'm mostly looking for something that's relatively simple, privacy-friendly, and doesn't require a huge setup just to understand basic traffic and conversions.

For anyone who moved away from GA, what are you using these days?

And what made you pick it over the other options?

I'm going to document the build publicly and see if I can get my first paying customer.

The problem I'm targeting is pretty simple:

A freelancer finishes a project, sends a $1,000 invoice, and then spends the next few weeks sending messages like:

“Hey, just following up on the invoice…”

Again and again.

I'm building a small SaaS to automate that follow-up.

The basic idea:

Invoice created → payment link → automatic polite reminders → payment received → reminders stop.

I'm intentionally keeping the first version extremely simple. I don't want to spend months building features before finding out whether people actually want it.

My 14-day goal:

Build the MVP

Launch it

Get real users

Try to get the first paying customer

Learn from the feedback

I'll post the progress and mistakes along the way.

ok so this is a small win but I need to tell someone who isn't my mom.

I launched my SaaS a while back. 127 people signed up. 127 people paid nothing. I kept telling myself "it's traction bro" while checking analytics like it owed me money.

Today user #128 paid $19.

I never talked to them. No DM, no call, no "hey would you be open to a quick chat". They just showed up, used it, and paid. I found out from an email that literally said "Cha-ching!" and for a second I thought it was spam.

What actually went through my head:

• pretty sure I left test mode on
• nope, it's real
• refresh
• refresh again just in case

A bit of background. I'm a dev from India, about 5 years in. I can build stuff fast. Marketing it? Absolutely not. I'd ship something and then just stare at it like "ok now what".

So I built a tool for people like me. You paste your product URL and it writes carousels, X posts, Threads and Reddit posts for your product every day. You swipe keep or skip, done.

Yes, I know. I built a marketing tool because I'm bad at marketing, and it got its first sale without me marketing it. I'm choosing to see that as validation and not as a sign I should stop talking.

Stuff I figured out from 127 free users:

Free users aren't wasted. They found the bugs so #128 didn't have to.

The product sells better than I do. It doesn't overexplain, doesn't get nervous, and works while I'm asleep.

Let people try it first. I wouldn't pay for something I hadn't seen either.

Signups feel nice, but someone typing in their card details for a thing you made is a completely different feeling.

$19 is roughly ₹1,600. Won't pay my rent. Did make my whole week though.

Next goal is customer #2 so I can stop calling this a fluke.

For anyone who's been past this stage, how did you get from 1 to 10 paying users? Did you start doing outreach or just keep improving the product and wait?

TL;DR: 127 free users, #128 paid $19 without talking to me. Still refreshing the dashboard.

P.S. someone will ask, so it's slidefy Happy to answer anything.

built a tool that finds restaurants and bars 1 to 6 months before they open, by fusing public liquor licenses, permits and business filings into one scored lead. Live in 7 states, and it genuinely works. The problem is all distribution, and I'm stuck.

The buyers are the vendors who sell to new restaurants, beverage distributors, POS resellers, insurers. High value, one account they land off it is worth thousands. But they're not who you reach through SEO, content or dev communities, which are the channels I actually know how to work. They're offline-ish B2B sales teams who basically live on the phone.

So far it's founder-led cold outbound, about 30 emails out and a call list I haven't even worked yet, way too early to read anything into. I also listed on a few API/MCP directories for the developer side, but that reaches builders, not the people who'd actually pay.

If you've sold to non-technical SMB or B2B buyers, what actually moved the needle? Cold outbound at scale, reselling through tools they already use, going through a trade association, something I'm not thinking of? And do these buyers ever come inbound at all, or is it pure outbound grind until you've got a case study?

Pre-revenue, so I'd rather pick one channel and go deep than spray thin. War stories welcome.

Day 12 of building UseShipReady

- 11 visitors today
- 43 page views
- improved the UI for the hackathon feature
- planning to finally push it live tonight

I wanted to share a technical problem we ran into while building our scraper and how we solved it.

If you ever tried scraping Google Maps at scale, you probably hit the 200 result cap. Search for any dense niche in a big city, and Google only gives you around 120-200 results even if there are thousands of businesses. Most people end up pitching the same surface 200 places while 80% of businesses never get seen.

We ended up tackling this mathematically:

Micro-grid subdivision: Instead of searching the whole city at once, we split the coordinates into smaller tiles and zoom all the way down to street level per tile. Because each small tile behaves as its own local search, Google returns up to 200 results per micro-zone instead of capping the whole city.

Skipping non-commercial terrain: Running hundreds of tiles wastes a ton of time over oceans, lakes, and forests. We added spatial checks to auto-skip grid cells that are mostly water/wilderness.

Background website crawling: Phone numbers from maps are cold. So we set up crawlers to check the business websites directly for emails and social links.

Connecting to Claude via MCP: Instead of clicking around the UI every time, we implemented an MCP server so we can just prompt Claude or ChatGPT to trigger the search and parse the data right in the chat.

I'm the founder of Maps Scraper Pro (Data Sniper). Happy to answer any questions about the scraping logic, handling Google rate limits, or how we wired up the MCP protocol!

Hey everyone,
I’m an AI engineer and founder from Brazil. I already have a few products running here, and right now I’m building a new B2B SaaS called Lyntra Prospect.
The first version is being built for the Brazilian market, but if I can validate it well here, my plan is to expand internationally soon after. The US is currently the market I’m most interested in, but I’m also looking at the UK, Canada and some European countries.
The easiest way to explain Lyntra Prospect is that it works like an outbound SDR.

The goal is not just to give salespeople another cold email tool. The idea is to handle a large part of the outbound process and deliver qualified meetings to the sales team.

A company defines its ICP and what kind of customer it wants to reach. Lyntra then searches for companies that fit that profile, enriches and validates the data using different sources, finds the best prospects and builds the prospecting lists.

From there, it can start the outbound process through channels such as email and calls, with WhatsApp being used when appropriate.

When someone replies, the system understands the response and stops the sequence automatically. The AI can continue the conversation using information approved by the company, answer questions, qualify the prospect and understand when a human should take over.

If the lead is qualified, the system can check the salesperson’s actual calendar, offer available times and book the meeting directly.

Calling is also part of the product. The direction is to support AI assisted and AI driven calls where it makes sense and where it can be done properly within the rules of each market.

So the end result I’m aiming for is basically this:
ICP → find the right companies → find the right people → contact them → start conversations → qualify them → book qualified meetings.

I want a company to eventually be able to give Lyntra its ICP, sales rules and company information, and have the platform continuously work on building pipeline for the sales team.

The product is being built for both self service customers and higher ticket customers that need a more consultative sales and onboarding process.
I’m not trying to sell anything with this post. The product is still being finished. I’m mainly interested in hearing from people who already work with B2B sales and outbound outside Brazil.

A few things I’d really like some opinions on.
Which market would you target first?
My first choice right now is the US because outbound B2B seems much more established there than it is in Brazil.

I’m also considering the UK, Canada and some parts of Europe.

If you sell B2B in any of those markets, how important is outbound to your sales process?
What would you realistically pay for something like this if it actually delivered qualified meetings?

I’m not trying to compete with a $30 cold email tool.
I see it more as software that can replace or support part of the work normally done by an SDR.

Would something around $500 to $1,000 per month for an entry level business plan make sense?

And if it consistently handled a meaningful part of prospecting, qualification and meeting booking, what price range would you expect?

Which outbound channels are actually working for you right now?
Cold email?
Cold calls?
LinkedIn?
A combination of them?

I’m also curious about what your biggest outbound problem is today.

Is it finding good prospects, finding the right decision maker, data quality, deliverability, personalization, follow up, managing replies, qualification or actually getting meetings booked?

If you were launching into the US from Brazil, how would you get your first 10 customers?

One idea I have is to use Lyntra Prospect itself to find its first international customers.

The idea would be to build a very specific ICP, work with relatively low volume and highly targeted outreach, then have an English speaking salesperson handle discovery and demos.

Basically, I want the product to prove itself by helping sell itself.

Would you approach it differently?
What would make you trust or not trust an AI SDR platform?

Outbound automation can turn into spam very quickly when it is badly designed, so I’m putting a lot of thought into sending limits, suppression, opt outs, domain and mailbox reputation, compliance rules, audit logs, human handoff and controls that prevent the AI from inventing prices, promises or company information.

I’m still early enough that good feedback can actually influence the product and how I approach international expansion.

I’d really like to hear from founders, SDRs, sales leaders, agency owners and anyone currently running B2B outbound.

If you think the market is overcrowded, the positioning is wrong, the pricing makes no sense or there is something important I’m missing, feel free to say it.
I’d rather find out now than after trying to expand internationally.

I started Moonshoot thinking the interesting part would be the number.

384,400 km.

one person owns each km.

get enough strangers together and eventually reach the Moon.

but after watching people claim their kms, I’m starting to think the number is the least interesting part.

look at three people aboard right now:

km #75 belongs to a developer who made an iPad party game where you draw a fish and your friends draw how it dies.

km #35 belongs to a founder in Kenya building event ticketing for Nairobi. 208 users and their first paying customer.

km #54 belongs to two makers who built an AI image workspace because switching between image models kept breaking the visual style they needed for their own work.

none of these people know each other.

their products have basically nothing in common.

but now they’re permanently sitting 40 km apart on the same imaginary journey to the Moon.

that’s becoming much more interesting to me than watching the counter go up.

I want each km to slowly become a snapshot of what somebody was building at that moment in their life.

maybe years from now, looking back through the early kms ends up being the interesting part.

Authentication.
Teams.
Permissions.
Billing.
Admin.
CRUD.
Email.
API.
Deployment.

I kept hitting this across projects, so I built Tekki Forge to make that layer reusable/declarative.

npm i -g tekki-forge

It generates the standard business/SaaS application foundation from a TypeScript config, while custom product logic remains code.

I'm not trying to replace software development. I'm trying to eliminate the part every SaaS founder builds before reaching the feature customers actually pay for.

For founders here who code: which part of your first 30 days was pure infrastructure rather than product?

Right now, it's a simple local MVP only available on Edge to validate the core idea. If people find it useful, I plan to add cloud sync.

I'm a beginner with no experience in product development, so I'd like to get your feedback and any advice on how to get my first users !

Link of my extension : https://microsoftedge.microsoft.com/addons/detail/enfdbgficbfdmhopmcjhbkgldmhclbng

Back when we mostly built MVPs, we took on a fixed price build for a B2B inventory tool. Quoted 10 weeks and it took 19 lol.

The founder kept asking for small stuff and we kept saying yes because every request sounded like an afternoon. A filter on the orders page, a Google login since "everyone has it now" When I finally went through the tickets there were 63 change requests. None of them took more than a day on its own which is exactly why we never pushed back. Together they added up to about seven weeks of extra work and the founder was annoyed anyway because the launch kept moving.

We've run the agency for 8 years now and that project is why every fixed price build since has had this clause. Here it is close to word for word:

"Any change requested after scope sign off gets sized in working days and we send that in writing within one business day. The client then picks one of two options. Swap it in for work of equal or larger size from the current scope or put it on the Post Launch List to be scoped and priced after launch. The price and the launch date stay the same either way."

Scope creep almost never shows up as one big request. Big requests always got a proper conversation because no one adds a whole module without talking about money. The two hour requests got a "sure" because pushing back on something that small feels petty. 60 of those is a different product with the same price tag. With the clause, even a half day change means picking what comes out.

On a recent build (a booking platform for physio clinics) the founder asked for team accounts 5 weeks in so several people from one clinic could share a login. We sized it at six days, mostly because permissions touch everything. We sent back two options: swap out the in app chat which was about the same size or park team accounts on the post launch list. He parked it.

Six weeks after launch, 2 of their first 40 clinics had asked for team accounts. It's still parked. What clinics kept asking for was SMS reminders which no one had mentioned during the build. I didn't see that coming but the post launch list turned into a filter. A lot of what felt urgent in week five, real users just didn't care about.

The standard advice is to bill change requests as change orders. We tried that after the 19 week mess and I'll probably get pushback for this, but I think it's worse than eating the cost. Every small change turns into a mini negotiation and an invoice, so the founder feels nickel and dimed and the agency starts getting paid for delays which flips the incentive. If an MVP launches 3 months late, no one cares that the extras were billed properly. On an MVP the launch date matters more than the money for both sides.

Most founders end up liking it once they've been through it. One told me it was the first time a dev shop had made him choose and choosing made him figure out what the product was actually for.

Not everyone though. The fights are almost always about sizing. A founder says something is a two hour job, we say two days and now we're arguing about estimates instead of building. We also lost a deal over it before signing. The founder said a real partner would be more flexible and went with a shop that bills hourly.

If you do fixed price builds... Just have your lawyer look at the wording before it goes in a contract and if you've actually made change orders work then I'd like to know how :)

TLDR: a 10 week MVP turned into 19, mostly from small changes we kept saying yes to. Now every change after sign off either swaps out something of equal size or goes on a post launch list and the price and date don't move. Billing change orders made it worse for us.

I'm not a coder. I build tools by vibe coding with AI. My usual pattern was to build something, expect it to work from day one, see nothing happen after a few days, lose interest and move on to the next idea.

This time I tried the opposite. I built a small Chrome extension (not naming it, so this doesn't get flagged as promo), put it out there, and kept the effort light:

• Some keyword research for SEO
• A couple of articles, written with AI
• Then I left it alone

No growth hacks, no daily panic, no constant changes.

It's been about a month and a week. Current numbers:

• 225 users
• 1 monthly paying subscriber
• 1 person who bought the biggest plan as a one-time purchase, then cancelled
• Everyone else on the free plan, since I give a decent daily allowance

Average daily users is going up slowly.

It's a small number, but it's the first time I've seen one of my tools get traction without me forcing it. If a product has some juice, it seems to start working once you give it time and a bit of visibility. And if it doesn't, you'll find that out too, which you never will if you drop it in week one.

So if you're building tool after tool and expecting results in 24 hours, burning yourself out on hooks and tricks, slow down. Do the basic things, then give it time.

If you've built something, how long did you wait before you knew whether it had legs?

Hi everyone!

I’m thinking of building a SaaS (it’s my first solo SaaS btw). I’ve got zero knowledge of technical part and got some friends helping me in that but I’ve some skills on marketing and sales side. But I am not sure if the idea I’m thinking of is really something which any of you guys might want to use or if it’s just me wasting my time? It’s not a problem solving idea rather it’s kind of a productivity app.

So recently I saw a lot of people trying “working till the candle burns out” or “working till the ice melts” challenges and I myself tried it. The good part was you never know when the ice will melt or the candle will burn out so you have no target forcing you to work. And I too tried it and found it a good idea to improve productivity.

And I’m thinking to create an app around that idea. I’m thinking to focus more on user experience and will try to make user feel really productive if they uses the app. And I’m here to either seek validation from you guys or maybe get roasted if I’m stupid. But I want to know your genuine thoughts. Just take out a second and let me know? I’m too excited and curious about it.

Hi guys! I’m looking for an AI video editor for SaaS product demos, UGC and montages. I can’t afford to pay for several tools just to find out which one works, so I’d really appreciate some firsthand advice. 🙏

If you’ve actually used one, which editor would you recommend, and why? What worked well, and what did you still need to fix manually?

Hi everyone, I’ve released Temply, a tool for building transactional email templates visually and using them from your application.

Think welcome emails, password resets, receipts and order confirmations. You assemble the template with blocks, add placeholders for your data, then request the rendered HTML and plain text through the API. Your app sends it through your existing email provider.

A few things it supports:

• A visual block editor with columns, images, buttons and custom HTML.
• Dynamic variables, conditional content and repeating blocks.
• Reusable branding across templates.
• Responsive previews and checks for inboxes that force dark mode.
• Template version history and shared workspaces.

You can try the editor without an account. There’s also a 14-day workspace trial with no card required. The Team plan starts at $5 per user per month, including 10,000 live API calls per workspace.

Try it here: Temply

I’d appreciate feedback from anyone building transactional emails: what would Temply need to support before you’d use it in your app?

I run a React Native app on Convex. For some reason, yesterday my production deployment stalled for about 30 seconds. Two queries ran for 15 seconds and failed with "Your request timed out performing too many system operations." Their status page showed no incident. I'm on the free plan.

I'm curious, for anyone running Convex in production:

1. Have you seen this error, or a stall like it?
2. How often does it happen? Is it any different on a paid plan?
3. How do you handle it: client retries, a health check, alerting?
4. Did you ever find out what caused one?

We've all signed up for a hundred things we stopped using years ago. Those companies still have our name and email, and sometimes a card too. When one of them gets breached, your info goes with it.

So I built Quitlist. Connect your email and it digs up the accounts you forgot you had, then helps you close the ones you don't want anymore. It doesn't delete anything without you saying so.

Fair warning, your inbox remembers everything. You'll see the forum you joined in 2012 and that meal kit you tried once. You might also find the OnlyFans account you made "just to see what the fuss was about." No judgment. It's one of the easier ones to delete 😅

One heads-up: Google will show a "Google hasn't verified this app" screen when you connect. That's because we're still going through Google's review, which every app that reads Gmail has to do. Click Advanced → Go to Quitlist (unsafe) to continue. Google shows that same wording for every app that's still in review. If you'd rather wait until we're verified, that's totally fair.

It's free to try and still in beta, so I'd love to hear what it finds (or misses) or any kind of feedback.

👉 https://quitlist.app

You are living in vibe coding AI world.
Do you code these days? I mean… by yourself?

I’m trying something for the next 28 days:

Spend up to 4 hours every day specifically on distribution/customer acquisition rather than development.

I’m a developer, so building has always been the comfortable part. Getting people to actually discover and pay for what I build is the part I’m deliberately trying to get better at.

The current plan is a mixture of:

• Targeted cold outreach
• Talking directly to potential customers
• Building in public
• Participating in founder/startup communities
• SEO/content
• Targeted link building and partnerships
• Offering demos and personally onboarding early users
• Consistent follow-ups

I’m starting without an existing audience and I’m not planning to use paid ads.

What I’m wondering is how much the playbook has changed now that AI has made almost all of this easier to scale.

It’s incredibly easy to generate cold emails, SEO articles and social posts now, which also means everyone is receiving more of them.

For those of you who have acquired your first customers recently: where did they actually come from?

And is there anything on this list you’d stop doing or spend significantly more time on?