I wanted a simple way to see my next bus and train departure without checking my phone every time, so I started building this. It shows live departures, delays and destinations in Germany and can be configured through HALTI App. Still very much being deployed, but this is the current version.

What feature would you add next?

Hey everyone,

A few months ago I shared the early concept of Expeditione here. Today, I wanted to share a closer look at the flagship expedition : Ancient Egypt.

Most educational content online is choked with cookie popups, ad banners, and auto-generated slop. I wanted to build the exact opposite : an authentic, ad-free digital museum you can explore straight from your browser with zero friction.

What’s inside the expedition :

• 5 Handcrafted Dioramas : Everyday homes, Nile farming, limestone quarries, temples, and the Giza Plateau.
• Interactive Tools : Dynamic scanner inspections, archaeological cutaways, and a 1:1 "True Size" mode at the Pyramids where you can stack structures up to 150m for real-world scale.
• Everyday Life Focus : Rather than just monuments, it covers how ordinary Egyptians lived, worked, and built.
• Classroom Resources : Downloadable educator guides and student worksheets with no sign-ups or email gates.

The Performance & Optimization Pipeline:

Getting interactive 3D to run butter-smooth on 6-year-old Chromebooks and budget mobile devices meant being ruthless with asset weight :

• Payloads: Initial core load is ~2MB, with subsequent scenes averaging ~1MB each (Pyramids sits around 2–3MB due to scale).
• Stack: Three.js, Blender, and GSAP for animation sequencing.

It’s completely free—no tracking, no ads, no paywalls.

Explore it here : https://expeditione.fun/expeditions/ancient-egypt/

Would be really glad to hear your thoughts on how you feel!

I hope you enjoy the expedition 💖

It’s only one star, but it’s my first one, and seeing someone I don’t know star something I made genuinely makes me happy lol

Realized 99% of my ideas are ass and I'm better off working a normal job and leaving the entrepreneur thing to you all. Still have a few days left before my Claude sub lapses, so I made an extension that, like its creator, has no utility. Kids love it though and it's good for a laugh when I forget I've got the stupid thing on, especially on news sites, so no ragrets.

Anywho. Good luck to everyone building in here, been a lot of fun seeing the cool stuff you all come up with. Hope every one of you become zillionaires, if you ever need a beta tester or a pair of bad eyes to review your work, give me a shout.

After years of "wait, did you feed Luna this morning?" arguments, I built an iPhone app called Petstead to put a single timeline of our pets care in one place.

It's deliberately boring on purpose:

• Local-first (works without an account)
• No AI, no care recommendations, no calorie math
• Just a clear plan, what was Last Done, and a factual receipt when you tap "done"
• Optional household sharing so my partner can accept coverage requests explicitly

The thing that mattered most to me was corrections don't quietly rewrite history. If I mark breakfast done at 8am but it was actually 7:30, I add a correction and the original fact stays visible.

Currently in TestFlight, free with one pet. iPhone only.

Curious — for the pet owners here, what would actually get you to switch from a notes app or memory to a dedicated tool? Or is "just remember" good enough?

Happy to answer technical questions too. Built it solo in SwiftUI/SwiftData.

I'm a solo developer and I've spent the last while building PDFz, a PDF scanner and editor for iPhone and iPad. Posting because I kept looking for one that doesn't send every page to someone's server, and ended up writing it.

What it does

• Scan paper with the camera: auto-crop, straightening, shadow removal, multi-page, ID card and passport modes
• OCR on the phone's own neural engine, so searching inside a scan works in airplane mode
• Edit text and images on the page, reorder and rotate pages, add watermarks and page numbers
• Sign with your finger, fill forms, tick boxes, stamp
• Merge, split, compress (you see the new size before you save)
• Translate a document, or point the camera at printed text
• Convert PDF to Word, Excel and PowerPoint
• A Wi-Fi desk: open an address on your laptop and drop PDFs onto the phone over local Wi-Fi, no cloud, nothing to install on the laptop

What stays on the phone

Everything above except one thing: Word/Excel/PowerPoint conversion runs on my server, because no phone ships with a layout engine that can rebuild a document properly. The file is deleted the moment the job finishes, the result is deleted when you download it, and nothing about the contents is logged. That's the only job that leaves the device, and it's written plainly in the privacy policy rather than buried.

No account, no sign-up. There's no database of you to leak because there isn't one.

What's free vs paid

Scanning, OCR, editing, signing, filling forms and search are free, with no account and no page limit. The free version shows ads.

Plus is $4.99/month or $29.99/year with a 7-day free trial, and there's a $1.99 week if you just need it for one document. It removes the ads and unlocks keeping the converted Office files, saving translated documents, merging more than two files, the smallest compression tier, passwords, form building, camera translation and the Wi-Fi desk. Previewing a conversion is free either way, so you can see the result before paying for anything. Those are US prices; your store may differ.

One more thing

It's in 49 languages, and Arabic isn't an afterthought: the whole app is right-to-left, and mixed Arabic/English documents keep their reading order when converted to Word. That was the reason I started building it.

App Store: https://apps.apple.com/app/id6754037398

Site: https://pdfz.ai

Happy to answer anything, including "why not just use Files or Notes". If something breaks, tell me here or at support@pdfz.ai. I read every message.

My side project has finally gotten to the point where the monthly numbers actually feel meaningful, which is great but I wasn’t expecting the timing of expenses to become such a headache. Early on everything was tiny. Now I’ll have a really good month and then a bunch of expenses seem to land together before all the money from that month has actually cleared. I’m starting to pay more attention to when money moves instead of just whether the month was profitable overall.

For anyone whose side project grew into something substantial, did you change how you handled expenses as it got bigger or just start keeping a larger cash buffer around?

I've had an app lock and photo vault on Play for a while, a thousand-odd installs. Went into GA4 in August expecting a retention problem and found something worse. 1,596 active users over 28 days. 1,469 of them opened the main screen. 36 ever reached the lock screen. 2.26%.

That screen only draws when a locked app is opened, so it's the share of people who ever locked anything at all. The 36 who got there are the best users in the dataset, 22 lock screens each and nearly three times the session length. The thing works. Almost nobody arrives at it.

The setup guide was the problem. Screen lock, then usage access, then draw over other apps, then device admin, then accessibility, all before you'd told it one app you wanted protected. Three of those are trips out into Android Settings and two sit behind system warnings written to sound alarming.

So the order is inverted now. You pick an app, the choice is saved, and only then does a sheet ask for the two grants actually standing between that choice and a working lock. Device admin dropped to optional. It guards against uninstall, the lock works fine without it, and it throws the scariest dialog of the five.

Whether any of that moves the number I don't know yet. Not enough people have been through the new flow.

https://play.google.com/store/apps/details?id=com.metacyberguru.securefolder

I've been thinking about this for a while.

There are millions of people online who know things we want to learn.

Someone knows Figma.

Someone knows how to code.

Someone knows video editing, marketing, photography, writing, a language, or almost anything else.

The knowledge is already out there.

But finding the right person to actually learn from can be surprisingly random.

You can search through Reddit communities, Discord servers, Instagram, LinkedIn, and other places.

You might eventually find someone who knows the skill.

But then there's another question: are they actually interested in teaching or exchanging knowledge with someone?

That's where the idea for my project came from.

I built a platform called Agora around a simple idea:

What if people could find each other based on what they want to learn and what they can teach?

For example:

* You know coding and want to learn UI/UX.

* Someone else knows UI/UX and wants to learn coding.

That would be a strong match because both people have something the other person wants.

With Agora, you create a profile, add the skills you can teach and the ones you want to learn, and then explore potential matches.

You can also filter people based on skills and location.

If you find someone you're interested in learning from, you send a connection request. Messaging only opens after the other person accepts it.

I kept that flow intentionally because I didn't want the platform to become another place where people could message hundreds of strangers.

The project is still an MVP. Agora

Hello everyone! Sooooooo, I wanted something small to have on my second monitor as company.

Not a game, not something I need to constantly interact with. Just a little companion that sits on my taskbar, moves around on its own and is there while I'm doing my own stuff.

It's called Cozy Paws. Right now it's a little cat that lives on the Windows taskbar. It has its own animations and can just hang around on its own, but you can also interact with it.

I recently put it on the Microsoft Store and I'm planning to keep expanding it with more pets, customization and small interactions.

The current version is completely free and includes one pet with all of its features. There is also an optional one time Plus upgrade for people who want additional pets and customization.

For now, I mainly want to see if other people actually like having something like this around while they are on PC.

Id love some honest feedback from anyone who gives it a try, especially whether you'd actually keep it running on your desktop.

Microsoft Store: https://apps.microsoft.com/detail/9PJ1DH037TCK

The length of a contract can create a false sense of certainty. A fintech founder can sign a three-year agreement with a banking partner, payment provider, or infrastructure company and reasonably assume that they now have three years of predictable commercial terms, but that assumption only holds if the economics of the relationship are actually stable for those three years.

I’ve come across agreements where the headline term is three years, but either party has a right to review or renegotiate pricing every few months. On paper, the relationship continues for three years, yet in practice, the parties are effectively reopening part of the commercial deal several times a year.

That distinction matters more than it might initially appear.

## A Long Contract Does Not Always Mean Long-Term Certainty

Consider what happens when a fintech spends months negotiating pricing with a critical partner, signs the agreement, completes the technical integration, and then builds its own operations around those economics.

The business may set its customer pricing based on those costs, enter into contracts with its own customers, hire employees, invest in infrastructure, and make growth decisions based on the assumption that the underlying commercial arrangement will remain reasonably predictable.

If the same agreement then allows the partner to revisit transaction fees, minimum commitments, or other important commercial terms every quarter, some of that certainty disappears.

The contract may still have three years left to run, but the business is repeatedly being asked to consider whether the economics that support its model might change.

That is not necessarily a problem with the duration of the agreement. It is a problem with what the duration actually protects.

## Review Rights Are Not Necessarily a Bad Thing

I do not think commercial review mechanisms are inherently problematic, particularly in fintech, where the economics of a relationship can genuinely change over time.

Transaction volumes may increase significantly, the scope of services may expand, regulatory requirements may introduce additional costs, or infrastructure expenses may change in ways that neither party could reasonably have predicted when the agreement was signed. Over a three-year relationship, the product and the business itself may also evolve considerably.

A contract should have enough flexibility to deal with genuine changes like these.

The issue arises when one party receives a broad right to reopen the commercial arrangement simply because a certain period of time has passed.

The fact that another quarter has ended does not, by itself, tell you whether the economics of the relationship have materially changed.

A more useful approach is to identify the events that should actually trigger a review. The parties might agree that pricing can be reconsidered if transaction volumes move substantially beyond an agreed threshold, if the scope of services changes materially, if a new regulatory requirement creates significant additional costs, or if a defined external cost increases beyond an agreed level.

Those are identifiable commercial events that both parties can understand.

"Another quarter has passed" is a much weaker basis for reopening a deal.

The distinction is important because a review mechanism should ideally respond to a genuine change in the relationship rather than become a routine opportunity to renegotiate terms.

## The Real Problem Is Often What Happens After the Review

There is another part of these provisions that deserves just as much attention as the trigger itself: what happens once the review actually begins?

A clause might say that the parties will review pricing every quarter, but that does not tell you what happens when they cannot agree on a new price.

Does the existing pricing continue until an agreement is reached? Can either party terminate the relationship? Is there a temporary pricing mechanism? Does the disagreement move through an escalation process? How much notice must be given before a proposed change takes effect?

Those details can completely change the commercial impact of the provision.

I tend to look at a review mechanism as a small negotiation process built into the larger agreement. You need to understand what triggers the process, what can actually be changed, how often the review can occur, what evidence supports the proposed adjustment, how much notice is required, and what happens if the parties reach an impasse.

The scope of the review is particularly important.

If an agreement allows a quarterly review of "commercial terms," that could potentially give the parties a much broader opportunity to revisit the relationship than a provision allowing them to reconsider one specific transaction fee after transaction volumes cross a defined threshold.

Those two provisions may sound similar during negotiations, but they can have very different consequences once the business has scaled.

## Changes Upstream Can Affect the Entire Business

This becomes especially important when the partner sits underneath your own customer relationships.

Suppose a banking or payments partner changes its pricing after you have already priced your product and signed customer contracts based on the original economics. Your customers may not care that your upstream provider changed its fees or that the contract allowed the change.

You still have to operate the product, pay your employees, maintain infrastructure, provide support, and deliver whatever you promised your own customers.

A change in one upstream agreement can therefore move through the entire business.

This is why I think founders should pay particular attention to pricing review mechanisms when negotiating relationships with critical fintech infrastructure providers. The question is not simply whether the provider can change its pricing, but whether your business has enough predictability to absorb that change without having to immediately revisit everything downstream.

## What Does "Three Years" Actually Protect?

This has changed the way I look at long-term fintech agreements.

When I see a three-year agreement, I do not think the most important question is simply, "How long does this contract last?"

The more useful question is, "How long are the commercial terms actually protected?"

Those are very different questions.

A three-year agreement with broad quarterly renegotiation rights may give you three years of contractual duration while providing considerably less commercial certainty than the headline term suggests.

That does not automatically make the agreement bad. There may be perfectly legitimate reasons for including a review mechanism, and in some relationships, some degree of flexibility is necessary.

But if the economics of the relationship are important to your business, the review mechanism deserves as much attention as the initial pricing.

## Build Flexibility Around Clear Triggers

Long-term agreements do not need to pretend that nothing will change.

In fact, the better agreements acknowledge that circumstances will change and establish a sensible process for dealing with those changes before either party is forced into an unexpected renegotiation.

That means defining what constitutes a material change, identifying which commercial terms can be reviewed, setting reasonable review periods, establishing notice requirements, and deciding what happens if the parties cannot reach agreement.

The objective is not to remove flexibility from the relationship.

It is to make that flexibility predictable.

When both parties know what can trigger a review and what happens afterwards, the agreement becomes much easier to manage as the business evolves.

## Conclusion

A long-term contract is only as predictable as the provisions that sit underneath its headline term.

A three-year fintech agreement can still leave a business exposed to significant commercial uncertainty if pricing, fees, minimum commitments, or other important terms can be reopened regularly without clear triggers or defined limits.

The lesson I would take from this is simple: when negotiating a long-term fintech partnership, do not only ask how long the agreement lasts. Ask how long the economics are protected, what events can change them, and what happens if the parties cannot agree.

The strongest long-term agreements do not assume that nothing will change.

They decide in advance what kind of change is significant enough to reopen the conversation, how that conversation will take place, and what happens if the conversation does not lead to an agreement.

That is what makes a long-term contract commercially useful rather than simply long.

I'm doing ten of these by hand, then I stop.

Reply here or DM me your answers and you get back one page: who it's for, the biggest assumption, the biggest risk, and one move for this week. I'll post the brief in the thread unless you ask me not to.

1. One sentence. What are you trying to change, and for whom?
2. Tell me about the last time someone in that group hit the problem you're trying to solve. What did they actually do?
3. If you had to bet on one thing being wrong about this idea, what would it be?
4. What's the smallest move you could make this week to find out?

Why these four: they're the ones I skipped on the things I built that nobody but me wanted. I built a framework around them afterwards. That's what writes the brief.

My best conversations about music have never been on music apps. They've been with strangers — someone at a party, a guy in a record store, a person in a comment thread who linked me something I'd never have found on my own.

Every music app I use turns that into a numbers game. Followers, playlist counts, monthly listeners. So I spent the last several months building the opposite.

It's called MusicPool. You pick a vibe, a genre, a mood, a decade. You get anonymously paired with one person who picked the same thing. You have 24 hours to talk and trade songs. Then the chat disappears, always. If you both want to, you can unlock each other's profiles before it goes, their name, what they're into, what other people have said about their taste. But the conversation itself is gone either way.

No feed. No followers. One stranger, one day, and whatever you played each other.

I'm the only person working on it, and it launched recently enough that I'm still finding rough edges. If you try it and something is confusing or broken, tell me here, I read everything and I'd rather hear it blunt than polite.

One honest catch: it only works if there are people in the pool. It's new, so matches can take a while right now. If the idea appeals to you, sending it to one person who'd be into it does more than anything else I could do on my own, the whole thing gets better the more people are in it.

I'm in the comments all day. Ask me anything about it, or just tell me the last song you'd want to hand a stranger, I'm curious what this sub would send.

Just bought a new place and got obsessed with figuring out the PERFECT floor plan, I even made a website for myself thats sims3 inspired where I can upload a floor plan and arrange it. I spent like 50 hours in a week this week lol

[https://planplan.me\](https://planplan.me) I dont want to monetize it, 100% free and will remain free if someone wants to have fun with it, enjoy

The idea itself definitely isn’t new. There are already a ton of affirmation apps out there. What I wanted to do differently was put a lot more focus on the design and the feeling of using it.

I wanted it to feel less like opening an app, reading a quote, and closing it, and more like having a small, calming moment in your day. So, I’ve been playing around with motion, visuals, interactions, and little details to make the experience feel more alive rather than just a collection of static affirmations.

It’s still a side project and I’m figuring things out as I go, so I’d genuinely love some feedback.

What do you think? Does the design/experience work for you? Anything that feels unnecessary, confusing, or could be improved?

https://soul-lift.net/

Would really appreciate any honest feedback, good or bad

Stackray is a website/url scanner that shows the technologies it detects, DNS records, subdomains, and other OSINT details.

Check it out: https://stackray.app

It's open source under MIT, and there's a one-click to deploy Railway template if you want your own instance for private scanning where you can also invite users into your instance, schedule recurring scans, track changes, and setup change alerts using resend (email alerts) and slack. Source code.

If you try your own site what does it get right or miss?

Ciao a tutti! Ho sviluppato Carburo partendo da un’esigenza personale: riuscire a gestire meglio manutenzione, scadenze e spese della macchina.

Tra rifornimenti, assicurazione, bollo, revisione e lavori fatti nel tempo, tenere uno storico ordinato diventa complicato. Mi interessava poter ritrovare facilmente quando avevo fatto un intervento, a quanti chilometri e quanto avevo speso.

Per organizzare queste informazioni, secondo me sono utili tre cose:

• Per ogni intervento: data, chilometraggio, costo e una nota su cosa è stato fatto, conservando la ricevuta.
• Per le prossime manutenzioni: tenere insieme scadenza temporale e chilometrica, seguendo le indicazioni del costruttore.
• Per le spese: distinguere carburante, costi ricorrenti e manutenzione, così da capire dove finiscono i soldi durante l’anno.

Voi come vi organizzate? Usate un’app, un foglio Excel oppure vi affidate ai promemoria dell’officina? Cosa trovate più difficile da tenere aggiornato?

Da questa esigenza è nata Carburo, l’app Android che ho sviluppato per raccogliere queste informazioni. Gestisce rifornimenti, consumi, spese e scadenze e permette anche di consultare i prezzi dei carburanti nelle vicinanze. È gratuita, senza pubblicità e senza account; lo storico resta sul telefono.

Per chi fosse interessato: Carburo su Google Play.

I originally just wanted to build a simple caffeine tracker. (Included a demo above)

But pretty quickly I realized that manually typing in the brand, flavor, caffeine amount, size, etc. every time you drink something gets annoying.

So I started building an energy drink database to make logging easier.

Then that turned into barcode scanning, drink pages, a website for the database, and now I'm thinking about what else the data could be useful for.

I always see post about people talk about how they start a small project but then they start adding feature after feature and it never gets "done."

I didn't think I would experience that until now.

Does this happen to anyone else?

Do you usually let the project keep growing when you see new possibilities, or do you force yourself to stick to the original idea?

My side project is a game where you run an AI company. Because it's a management/economy sim, the screen is inherently full of numbers, charts, cash balances, and tables.

I just redid the whole interface, and now I'm too close to it to judge one thing : does this read as a game you'd want to play, or as enterprise software?

So, gut reaction only :

• First glance : game or work?
• What one element makes it feel like (or kills) a game?
• If it's reading too corporate, what would you change first?

It's live here for free, no signup :

https://lordoftokens.com/

just curious—what tools do you guys usually use when building products?

i mostly use n8n and openai. claude looks great, but i always seem to burn through the usage limits pretty quickly. now that astra is out, i haven’t really felt the need to use it.

any tools you’d recommend? doesn’t have to be AI-related.

Hi! I was creating a new version of my app, total pivot to be focused on one thing. While doing it I had a lot of pull backs on whether I should be putting features as premium.

For context, my app is offline-first, you dont really need to use internet unless you want extra features, but even that is user controlled.
Backup? iCloud/Google Drive
AI Interactions? Apple Intelligence/User’s Gemini API Key

So there isn't really a meaningful cost to me per user, and I have a hard time charging people for something when I know they can already get it for free.

I ended up making everything free and it just got approved to the App Store today.
Did I make the right decision?

For now, the app is mainly gonna be used personally and by family members, so I'm not really concerned about making money from it. Of course it took a lot of time to build, but I don't really count that as a cost since ideally this is something I wanted to build for myself and my family anyway. It's a side project, not really work for me.
I'm mostly just happy that I finally got the thing out there.

But I'm still wondering what I should do if it actually gets users. At what point do you guys think it's reasonable to start charging? And what would you even charge for in this kind of app?
I'm thinking maybe a cloud service makes more sense since that's an actual ongoing cost, but I'm curious what other indie devs would do.

Did I make the right decision making everything free?

I'm building Felan, an open-source, model-portable coding agent built on Pi. The goal is to get software work done correctly with less model spend, rather than chase a lower token count on its own.


The harness combines model routing, progressive context, compact tool output and explicit task state. We want to reduce waste around the model without treating a cheaper failed run as a win.


Across six controlled, extension-specific comparisons, we measured 36.6% lower aggregate model cost against disabled baselines. These weren't comparisons against other coding agents or a test of all extensions enabled together. The RTK comparison also had one timeout: 5/6 candidate runs passed versus 6/6 baseline runs, so I wouldn't present the cost result as proof of equal reliability.


Felan is MIT-licensed and doesn't require a Felan account. You can run `npx @felan-ai/felan` with Node.js 22.19 or newer and a supported model-provider account or API credential. It runs with your host permissions, not inside a sandbox.


Repo: https://github.com/felan-ai/felan
Benchmarks: https://felan-ai.github.io/harness-bench/results/2026-09-felan-extensions/


Where do your current coding agents waste the most work: context, tool output, retries or something else?

The app turns speech into text. Getting it from someone's downloads folder into their working day is proving to be a different problem.

I shared Typeglot with a few contacts, but only one is actively testing it. I'm grateful for that person. I'd also quite like a sample size that doesn't depend on one person's calendar.

Typeglot is my Windows 10/11 dictation app. It puts speech into text where you're working, including a mode that lets you speak one language and produce text in another.

So I'm opening a small beta for 8 to 12 people outside my circle. Use it in real work for 14 days, without daily reporting. I'll then email one evaluation, with five days to complete it.

Selected testers get free beta access. Completing an honest evaluation qualifies for a six-month complimentary licence after eligibility review. "I tried it and went back to typing" is a perfectly useful verdict. Positive feedback isn't required.

Technical and non-technical users are welcome, whether you work in one language or several.

Application: https://typeglot.com/extended-beta/

You can also register optional interest in the future affiliate programme. No following required; no effect on beta selection.

Fellow makers: what got your testers past the download and into a second day of actual use?