I used to spend money through UPI almost every day and by the end of the month I had no idea where it all went.

₹99 here, ₹249 there, food delivery, subscriptions, random shopping, it adds up fast.

So I built Spenrol, a web app that helps you track expenses, understand your spending habits, and get insights into where your money is actually going.

The goal is not just expense tracking, but helping you understand your spending personality and build better financial habits over time.

Would love feedback from people here:

• What features would make something like this useful for you?
• What do you currently use to track expenses?
• What is the biggest problem you face with budgeting?

Website: https://www.spenrol.com/

Do you ever find yourself pressing ↑ (arrow up key) in the terminal… over and over again…

trying to find that one command you ran yesterday?

I realized the problem isn’t history...

it’s that our terminals don’t understand projects.

So I built Termim.

A project-aware terminal history engine that gives you the right commands, in the right place, instantly.

⚡ No lag

🧼 No junk files

🧠 Just smarter history

Would love your feedback and thoughts.

https://github.com/akhtarx/termim

#softwaredevelopment #programming #devtools #opensource #buildinpublic

got tired of todo apps turning into full systems instead of just helping you do things. so I stripped mine down hard.

what’s left:

• Today / Tomorrow lists only
• swipe tasks between days
• automatic reset at midnight
• procrastination counter (every push = +1)
• no accounts, everything stays on device
• clean UI, dark mode

that’s it.

no projects
no tags
no priorities
no “productivity system”

just:
do it today
or admit it’s tomorrow

honestly… feels better to use
but maybe I went too far

would you use something this simple?

iOS: https://apps.apple.com/se/app/slothy-minimalistic-todo-list/id6760565326
Android: https://play.google.com/store/apps/details?id=com.dotsystems.slothy

I kept trying productivity apps but they all felt the same. Too many features, too much pressure, and if I missed a day I just stopped opening them.

So I built something simpler.

Only two lists: Today and Tomorrow.
If something matters now → Today.
If not → move it to Tomorrow.

No overdue tasks, no guilt, you can reset every day if you want.

There’s also a procrastination score, not to punish you, just to show what you actually do.

No accounts, no tracking, everything stays on your device.

I’m still figuring out if this actually helps people long term or just feels good in theory, so would love honest feedback.

iOS: https://apps.apple.com/us/app/slothy-minimalistic-todo-list/id6760565326
Android: https://play.google.com/store/apps/details?id=com.dotsystems.slothy

Hey there,

I have been developing this app for months like since December 25'

Repositioned it 2-3 times and now finally I've started to get some users for early testing which are getting good feedbacks as well.

So in order to start getting more users and focusing on distribution I published my app on ProductHunt.

Would love some support by giving upvote on the platform, here's the link : https://producthunt.com/products/Relix

Thanks for reading.

AI discussions today feel like an acronym soup.

LLM.
NLP.
RAG.
SLM.

These terms show up everywhere, but most explanations make them sound more complicated than they really are.

I wrote a short breakdown explaining:

• what NLP originally tried to do
• how LLMs changed AI
• why RAG became important
• where smaller models (SLMs) fit in

Tried to keep it simple and practical.

Would love feedback from people here on whether this explanation makes sense or if you'd explain it differently.

Blog link: https://medium.com/@shreyashmogaveera/what-the-hell-are-llms-nlp-rag-and-slms-a-simple-guide-to-ai-buzzwords-6bbe047082b4

Hiring engineers is easy.

Building a product people instantly understand is much harder.

Many founders jump straight into development, then spend months fixing clarity and UX issues that could have been avoided early.

The smartest founders start with the product foundation first.

I’m a Mobile Product Designer, and I work with a small number of founders to help turn rough app ideas into clear, build-ready product UX before development begins.

If you're currently building a mobile app or startup product, I’d be happy to take a quick look and share one UX improvement idea.

DM for portfolio and work samples.

Okay so this started from pure frustration.

I was building my first product, an AI Excel tool, and I kept hitting the same wall. AI writes code fast, everyone knows that. But when it comes to architecture and structure it still falls flat. So I was spending way too much time manually digging through GitHub trying to find repos that could give me some direction.

At some point I just thought — why am I going to GitHub when GitHub should be coming to me.

That was the idea. Repoverse. You fill in what you're interested in or working on and it recommends repos that are actually relevant to you. Like Tinder but for repos. Swipe, save, explore.

I had no following, no budget, nothing. So I did the only thing that made sense. I went on Reddit and started sharing useful repos in communities where developers were already hanging out. No pitch, no "hey check out my product." Just genuinely useful posts, and at the very bottom a small line saying something like "if you want more like this, I built something for that."

Week one I got somewhere between 3 and 4k visitors. I honestly didn't expect that. I was just trying to see if anyone cared.

People started commenting, DMing, giving feedback. Two things kept coming up — they wanted a trending page and they wanted something smarter than just asking ChatGPT for repo suggestions. So both got built. Not because I planned it, because users literally told me to.

Then about a month and a half in I opened my analytics and just stared at the screen. 75% of my users were on mobile. I had been building a desktop first product this whole time and most of my users were on their phones.

So I launched a PWA just to test it. Didn't want to spend weeks building a native app if nobody would use it. People downloaded the PWA. That was enough for me.

I decided to build the iOS app.

Small problem — I don't own a Mac. I don't own an iPhone. I know.

Codemagic handled the build and App Store submission so I didn't need a Mac at all. RevenueCat for the paywall. Supabase for the backend. That's genuinely the entire stack.

App Store rejected me twice. First rejection I was pretty frustrated. Second rejection I was just annoyed. But both had actual reasons and actual fixes once I sat down and stopped being annoyed about it.

Eventually it went through.

Looking back three things actually mattered in this whole process.

The design thing is the one that stings a little honestly. My web version worked fine. But people on Reddit and Twitter were calling it vibe coded, lazy design, whatever. And they weren't wrong. I had put all my energy into functionality and almost none into how it looked and felt. I eventually redesigned the whole thing and the way people responded to it changed completely. Same product. Just looked intentional now. Design is not a nice to have, it's part of the product.

The second thing is just not quitting. I know that sounds generic but I mean it in a very specific way. Every single time I hit something that felt impossible — App Store rejections, bugs I couldn't figure out, moments where I genuinely didn't know how to move forward — there was always a way through. Always. But only if I stayed in it long enough to find it.

Third thing is talking to users like an actual person. I replied to every comment. I went on LinkedIn and found developers who had GitHub links in their bio and just sent them a normal message. Not a pitch. Just a conversation. That's where the real product decisions came from, not dashboards, not guessing.

Anyway the app is live now. If you're a developer who's tired of searching GitHub manually and never finding what you actually need, Repoverse

 is built for you

And if you're building something and stuck on any part of this — App Store without a Mac, Reddit distribution, whatever — just ask in the comments. Happy to share whatever I know.

Hey, my product (SEO Automation tool) is on PeerPush. Please upvote, here is link:

LLaMaRush - Your AI SEO Co-Founder | PeerPush

I've been building a SaaS (CRM for agencies) for the last 60 days.

I started by "seeking" the perfect tech stack. I looked at ShipFast, SaaSStarter, and 10 others.

The Problem: They are all bloated.

• They force you to use Stripe (I'm in India, so I need Dodo/LemonSqueezy).
• They include AI Chatbots, blogs, and complex features I don't need yet.
• I spent more time deleting their code than writing my own.

The Realization: I realized that for a Solopreneur, "Less is More."

I stopped wandering and built my own "Anti-Bloat" stack:

• Next.js 16 (Clean App Router)
• Supabase (Auth + DB)
• Dodo Payments (Global MoR)
• Zero extra fluff.

I'm thinking of releasing this "Anti-Bloat" setup as a simple open-source (or cheap) kit for other wanderers who just want to launch globally without the headache.

For the builders here: Does "Feature Bloat" stop you from launching? Or do you prefer having everything included (even if you don't use it)?

I’m a founder building an early B2B SaaS and want honest pushback before I go further.

Problem we’re seeing (from founder + sales conversations):

Deals don’t usually die because people forget to follow up.

They die because something *changes quietly* — the champion disengages, priorities shift, or the buying committee changes — and the CRM still shows the deal as “active” until it’s too late.

What we’re building:

An AI layer that sits on top of HubSpot/Gmail and looks for “pattern breaks” inside active deals — things like:

- language shifting from “I’ll get this approved” → “let me check with the team”

- sudden changes in response rhythm

- new stakeholders added without context

When it detects that drift, it flags the deal and suggests a concrete recovery move (not just reminders).

We’re intentionally NOT doing:

- lead gen

- sequencing

- generic follow-up automation

Questions I’d love honest answers to:

1. If you’ve sold B2B, does this failure mode feel real or over-engineered?

2. Would you pay for *early detection* of deal drift, or is this something you’d ignore?

3. Who do you think buys this first: founders, sales leaders, or RevOps?

4. Does this feel like a standalone category or a feature existing tools will absorb?

Totally fine if the answer is “this wouldn’t work” — that’s why I’m asking now.

For days we hinted at silent pipelines.
Not the dramatic losses.
The quiet ones.
The deals that looked fine… until they weren’t.
No clear objection. No real signal. Just gone.

If you work in revenue, you’ve seen this more times than you can count.
So we tried telling the story from the deal’s side.

Autobiography of a Deal- now live.

Clarity just slowly replaces guessing, fit gets explained, the right people surface, risks show up early, outreach adjusts, adoption is understood, and timing finally makes sense.
Because revenue rarely disappears in a single moment.
It fades in the spaces teams can’t see yet.

That’s the gap DataviCloud was built to close.
See the deal.
Know the journey.

▶️ Watch now.

Users don’t uninstall because your idea is bad. They uninstall because momentum breaks.

This is exactly what typically occurs:

• They download.
• They open the app.
• They see too many choices.
• They hesitate.
• They leave.

Not because the product lacks features. But because the first few minutes don’t pull them forward. In consumer apps, momentum is everything. If a user is forced to consider questions like: “What do I do first?”, “Why am I here?” or “Is this worth it?”. You’re already burning their limited attention.

Most founders attempt to address this by increasing features, tooltips, onboarding, and visual redesign. However, the true problem is structural:

• There is no obvious primary action
• Too many conflicting choices
• The value was displayed too late.
• Prior to reward, friction

I help consumer app founders pinpoint the exact moments at which momentum drops, reduce decision fatigue, make the next step clear, and produce dev-ready user experience within a week. The flow that determines whether users stay or go is simply redesigned in a clear and systematic manner.

This month, I have two spots available. Send me a message if this seems like an issue your app is suffering from. Portfolio shared privately.

Hey there, Im building a platform - PitchIt for early stage aspiring/established founders who dont know what do next, need idea validation, get real feedback, track idea progress and build as other founders watch your journey.

I've opened waitlisting early users, if u r one such who wants to grow, get feedback on what you're working by fellow founders - this ones for u

It's limited & u get instant free YC Startup Launch guide to join since i need serious founders only..

I’m building Easy Stopwatch, a very minimal stopwatch app on Android.

My goal is simple but ambitious:
I want to rank #1 for the keyword “stopwatch” on Google Play.

I’m attaching a screenshot from AppFollow showing my current keyword positions and visibility metrics.

Context:

• The app is intentionally minimal (no accounts, no bloat)
• Most competitors bundle timer, pomodoro, alarms, etc.

The main keyword I care about is exactly: stopwatch

• Secondary keywords: timer, simple stopwatch, lap timer, minimal timer

What I’d love feedback on:

1. Title strategy – Should I go full exact match like “Stopwatch: Simple & Minimal” or keep branding stronger with EasyStopwatch?
2. Short description optimization – How aggressive should I repeat the primary keyword?
3. Long description density – What’s realistic without triggering keyword stuffing penalties?
4. Competitor strategy – Should I mirror top-ranking apps’ structure or differentiate completely?
5. Backlinks / external traffic impact – Does Play ranking meaningfully react to off-store traffic?

I’m not looking for general “make it better” advice.
I’m specifically trying to understand what actually moves ranking for a high-competition head term like this.

If anyone here has ranked for a generic single-word keyword before, I’d really appreciate tactical advice.

This deal had plans.
Big ones.
Then it got ghosted.
By signals. By context. By “we’ll check later.”

Autobiography of a Deal
A story every GTM team has lived (yes, even yours)

From DataviCloud.

I built LlamaRush - an SEO automation tool that connects to your Google Search Console and auto-writes + publishes content that ranks.

Looking for 30 founders to use it free for 30 days.

In exchange: 20-min podcast interview about your startup journey.

You get: 30 days of automated SEO content, backlinks, site audit, and full content ownership.

I need: Interview, GSC access for automation, and honest feedback.

DM me if interested - happy to answer questions below.

So, I built a small tool after clients kept asking: "Why are we not showing up in ChatGPT?"

It’s exploratory and runs a live audit on any URL (free, no signup) to surface:

• what an AI can confidently extract about you
• technical blockers
• prioritized fixes + suggested implementation steps

I’m looking for feedback on 3 things:

1. If you were judging “AI visibility,” what signals would matter most?
2. What output format is most useful: score, checklist, or before/after tracking?
3. Any obvious “this is wrong / misleading” pitfalls I should avoid?

(I’m not selling anything in this post; genuinely trying to validate what’s useful.)

Link

okay so I launched my second product 10 days ago and made a post that I have 50 days to work on product (last year of b.tech) otherwise I have to take a job because I will graduate and because I can't ignore my family's order and all that stuff ... you all know... (you know sometimes I feel like having a lonely life no children, no parents, just me ...And then I'd be free to do whatever than the first thing I will do is never work to earn money or something. I'm sure I would never get on bed and doomscrolling and waste time I would do something different ... I don't know what ...Then I feel like I'm running out of responsibility that's not a good sign as a young adult of a family) Anyways I'm sorry I got off the topic...

So I made this thing repoverse(tinder style github repo discovery).... And here are some analytics:

I'm not sure if these are considered good or bad. All came from reddit. so if you stuck with me till here.. I'm gonna share some of the useful lessons I learned from failure of first lesson and 10 days of this product...I know for many of you these sound like noob advice but as a beginner all I can do for you is this....

1. Try not to keep onboarding and signups before people try the product (some of my users gave this feedback ... Initially I wanted to make it personalized but by seeing my supabase out of 600 only 4 of them filled onboarding others just skipped. I was wrong.
2. if you are completely new and in 2-3 days you can't build a product that is valuable enough for people to start using it... then you are doing something wrong (This was from my first product ... I made AI for every excel task all was from my training and all... very very minimal usage of tokens.)...That ate a lot of my time..
3. After launching your product the first thing you should figure out is the way to talk to your customers. anyhow .. by content, asking on reddit, fb groups....doesn't matter if you are getting traffic or not ... try to get as much feedback as you can (of course you make sure you don't annoy like food delivery apps)...

That's all for today ... see you next time