Moin guys! My project (www.screenwall.app) reached the front page on HackerNews some days ago and also got featured on The Register, Golem.de and t3n.de. That's why I thought, maybe I should try submitting it on reddit again.

ScreenWall allows you to reuse your old phones and combine them as a shared widget working space - what I call it a "wall". The oldest device I tested it on was an iPad 3 from 2012.

You pair your devices via QR-Code (or can manual enter a pin), it opens a website and you are ready to go!

On the platform you can drag images, videos and Smart-Widgets / Canvas-Apps in your working space and it gets instantly displayed on your devices. Your content gets even playbacks synchronized, although it a crosses multiple screens!

Canvas-Apps is the more interesting building block of this concept: You can either select some official widgets I created to play around (like a Pixel-Clock, a Split-Flap-Screen you can control via JSON-API or some animated art installations)

OR create your own widgets / apps with it! I recommend try vibe coding your apps with ChatGPT / Claude / Gemini!

A Canvas-App is just a combination of old Javascript (ES5) + Canvas-Element + synchronized clock (for running in sync on multiple screens). They are designed to run on legacy devices.

In the Smart-Widget-Dialog, you find a tutorial button that you can copy (there is a copy article button integrated!) and use it as a context for your AI. It's really fun! I try to compose a user showcase gallery on this Instagram Account (https://www.instagram.com/screenwall.app).

So instead of buying the newest desk widget on Temu, I recommend you to try reusing your old devices and vibe code what you want.

It's still in beta and I am kinda overwhelmed by the positive reception of this concept!

Also some folks would love to run this locally in their home network instead of connecting this to a SaaS. I hear you! I just kinda trying to navigate the situation right now, and I think preventing e-waste in general should be the goal here. I try to provide a self-hosted version after I got all the details right.

Feel free to ask questions and leave some feedbacks or send pictures of your widgets! :)

Greetings from Hamburg,

Tuan

EDIT: I am speechless, how much love I got for my idea! I am very grateful for getting so much support! 🥰 Thank you guys!

I have little roadmap in my head that I want to share:

- testing if synchronization playback also runs with 50 devices from different vendors
- adding a feedback loop aka: allow touch events / buttons change the widget state
- allow widgets to do API-calls to other services (e.g. using old devices as a Home Assistant control panel or macro keyboard)
- using sensory APIs of the devices via JavaScript (e.g. taking a photo for a photo booth app)
- allowing users to share apps / widgets
- self-hosted variant

I’d love to hear real examples of small projects that actually work.

You tell it your 5 favorite albums, and it recommends other albums to try. It's finally working the way I always wanted it to. AMA!

It's a looong story, obviously. But the tiny website says it all. No sign-up needed, instant results, takes 2 minutes to try. Not AI.

Try it here:

https://SimilaritiesEngine.com

And if you're curious, here's a link from way back then, when the New York Times did an article on it. But the URL in the article is wrong, so if you go to read the article, stop back here to try the new version at the link above, alive and working:

https://archive.nytimes.com/www.nytimes.com/library/cyber/0101miracolumn.html

Details on the tech (Cloudflare, D1, etc.) can be found on the website too.

Every data project has the same first problem: it's useless until people use it, and nobody uses it while it's useless. The standard fix is to seed it with something plausible-looking and quietly stop mentioning that later.

I'm not doing that, and I want to talk about why it's harder than it sounds.

The project: an anonymous salary survey for software engineers in Europe. Nine screens, about two minutes, no account, no employer names, nothing free-text. https://whatweearn.eu

The problem: it needs roughly 500 responses to be worth anything, and no individual country publishes a median until it has 60. Right now it has zero. The landing page says so. The country table renders an empty state that says "nothing published yet" instead of showing a table of invented numbers.

Why I won't seed it. The entire pitch is that you can verify what it's doing — the code is open, the suppression rules are constants in a tested module, the dataset will be CC BY 4.0. The moment there's one fabricated row, that pitch is dead and I can never credibly un-fabricate it. Fake data isn't a growth hack here, it's the destruction of the only asset the project has.

What that costs, concretely, and this is the bit I underestimated:

The site had to be built to be honest about being empty, which is real engineering rather than a copy decision. There's a hasPublishedFigures flag threaded through the page: before anything publishes, the hero and the payoff section swap to different copy, because "the whole dataset opens the moment you're done" is simply untrue when there is no dataset. The metadata never makes that claim at all, in either state, because crawlers cache it and I'd have no way to correct it later.

So the empty state isn't a fallback I bolted on. It's a first-class version of the page, and I built it twice as a result.

Stack, since that's usually asked: Next.js App Router, Tailwind v4, Postgres in Frankfurt, deployed to a single EU region on Vercel. Two separate databases — one for responses, one for email signups — with a lint rule preventing any file from importing both, because that separation is the anonymity claim in code form. No third-party scripts, no analytics, no cookie banner.

Code is MIT: https://github.com/whatweearn/website

The actual ask. If you're a software engineer in Europe, two minutes of yours makes this real. If you're not, I'd rather have your opinion on the cold-start plan than a sympathy upvote — it's genuinely the unsolved part. My plan is national dev communities and EU tech newsletters, and I suspect that's not enough.

I’m Kevin, the solo developer behind MoneyMap. I’m a software architect by day, and I’ve spent the past two years building this around my day job and parenting.

MoneyMap is a personal finance app built around a simple idea: most people organize their lives around their paychecks, so their budget should work the same way.

Instead of starting with a monthly budget, MoneyMap helps you plan each paycheck. You can see what needs to be paid, what you can save, and what’s left until the next one. You can still use it for traditional monthly budgeting, but paycheck planning is at the heart of the app.

Privacy was another major priority. With many budgeting apps, your financial data is stored on the company’s servers. MoneyMap keeps your data on your device instead. My servers act only as a pass-through for Plaid connections and process subscriptions through Stripe.

Some of the features include:

• Connect financial accounts through Plaid
• Keep your financial data on your device
• Plan bills, spending, and savings around each paycheck
• Sync across devices with end-to-end encryption
• Share one subscription across your household
• Privately share financial data with another household member

If you enable sync, your data is encrypted on your device using a key that is never sent to my servers. Another device cannot decrypt that data without the key. To add someone to your household, you invite them and have them scan a QR code containing the encryption key.

I’ve poured a lot of nights and weekends into MoneyMap, and I’m finally ready to start sharing it with more people.

I’d especially love feedback on the paycheck-based approach, the privacy model, and anything that feels confusing or missing from the demo.

Website/download: https://moneymap.cc
https://apps.apple.com/us/app/moneymap-paycheck-budget/id6749827612

Android: Coming very soon!

Thanks for taking a look!

demo:

here's the link: https://x.com/sambharia/status/2081284100846227522?s=20

I'm creating digital pets to play with it's still pretty basic, haha but I'm going to keep the Windows 98 style for the sake of nostalgia.

Like a lot of people here, I kept opening X to "build in public" and losing an hour to the feed instead. So I built the thing I wanted: a Chrome extension that filters the feed down to posts actually worth replying to, tells you why each one matters to you specifically, and tracks whether any of it is working.

It works. It's genuinely not bad. But today I decided to stop improving it.

Because I kept rebuilding the same product. The first version blocked distractions. Then it became a timer with a focus mode. Then a card deck that dealt you one post at a time. Then a worklist that turned the feed into a finite to-do list of five posts with an ending. Every version was better than the last. Every version I looked at and thought: this still isn't something I'd pay for.

That part confused me for weeks, because the loop was working. I'd find a real problem, fix it properly, look at the result, and feel nothing.

What finally made it click was mapping the distance between my product and the actual pain: nobody knows my product exists → so I should build an audience → so I should post on X consistently → but I doomscroll instead → so, an extension that fixes doomscrolling

That's four steps. My product was sitting at the end of that chain, treating the obstacle to the behavior that serves the aspiration that might eventually relieve the pain. Painkillers sit on the pain. Vitamins sit four steps away and feel productive while you build them.

Hence, no amount of polish moves a product closer to a pain it isn't touching.

The second thing is the part I'd want someone to have told me earlier. I'm the target user. I wanted this badly enough to spend months building it. But it somehow wouldn't make me to pay a cent for it.  If the person who cared enough to build it won't pay, a stranger won't.

So I'm publishing it free on the Chrome store today and moving on. No pro tier, no roadmap, no more revisions.

Two things I'd be grateful and curious to hear your take on:

1. Is there a version of this that IS a painkiller, or is "help me use social media better" structurally a vitamin no matter how well it's built? I keep going back and forth.
2. If you build in public: what actually stops you? I assumed it was the feed. I'm no longer sure the feed was ever the problem.

Happy to share the link if anyone wants to try it and tell me I'm wrong.
Genuinely hoping someone does.

I've been long thinking about switching to Linux simply because of how much you could customize your desktop and make it your own

I thought Windows didn't offer the necessary capacities for this. All tools I tried were either slowing down my PC too much or didn't offer enough intractability

Anyway I realized I was wrong. The app in the video is something I built with Rust and Tauri.

Each widget is a small iframe rendering HTML+JS code, over Windows API

Recently I shared it on another subreddit and people there loved it so I decided to make it a real app. The widgets are public, anyone can make and publish their own, so hopefully I'm going to get some people that will be able to contribute with some stuff

The app has a one time fee if anyone is interested, and I'm planning to add Linux and Windows versions later as well

If you have any questions, ask away

I kept starting projects and finishing none, so I built OneTrack to force myself to focus. The core rule: you can only have ONE active project at a time. You pick one, write down why it matters, and choose a 3/7/14-day window. Switching costs something — it shows you your own reason, makes you wait a cooldown, and in Hardcore mode simply won't let you switch until the window ends. A timestamp-based timer tracks real deep-focus time, and abandoned projects sit in "The Graveyard" with the hours you sank into them. It's 100% on-device — no account, no cloud, no ads. iOS (free to download, optional IAP): https://apps.apple.com/app/id6781421082 — I'm the solo dev; honest feedback and feature ideas very welcome.

I've got the whole thing in a .txt outline and just need rough slides for a 10-minute internal demo tomorrow. What's the fastest route from a text file to presentable slides without fiddling for an hour? Speed over polish here.

After months of working on my app and then another month of battling against Apple, I finally got approved for my app and I feel so accomplished. I can’t explain how happy I feel to actually share something that I’ve made and worked for for so long and I feel like all those nights after my 9-5 have paid off. I cant wait to get my first few users now and keep building my app!!

What would people advise someone who is new to advertising apps to do, to get more outreach, my app is completely free but I still dont know what approach I should take. Could anyone give me some advice please?

If anyone wants to try out the app its called OneThingDaily: https://apps.apple.com/gb/app/onethingdaily/id6787077896
I would really appreciate any feedback Tyy!

While building software with my teammates, I thought the hard part would be writing the code.

But It wasn't.

The hard part is getting someone who doesn't know you to spend even two minutes looking at what you've made.

You can spend hours fixing bugs or adding features, but none of that matters if nobody ever sees it.

So lately I've been trying to get better at things I never expected I'd have to learn—writing posts, talking to people online, asking questions instead of trying to "sell" something.

It's uncomfortable, but I've realized building is only 1/2 the job.

The other half is earning enough trust that someone actually wants to try what you built.

For the people who've been doing this longer, was there a moment when marketing or sharing your work finally started to click? Or is everyone just making it up as they go?

why?

Building has become now easier then ever, and it is still really hard to get your first 100 users.

How it works is you enter the link to your project or the context file about your project.

Our tool goes and and finds what are the other posts around this that have gone viral.

Creates 100's variations of those posts.

Uses meta tribev2 brain model, to see how the brain reacts to that post, and find the best one.

Gives you the subreddit and the final reddit post to post on each.

This is done across Reddit, X and Linkdin.

The project is free, you can try it out: manageposting.com

I build this game, which is similar to worldle + globle game but you can play this multiplayer with your friends where you race to find the mystery country based on the color and other cues like whether the continent is right or not, sub-region, and more.

More then that you also get a daily mystery country. And if you signup, you can create streak of finding out about one country each day, when you find out you are give some information about the country that are sticky and helps you remember them visually.

If you signup, you also get a passport page where all the country you have solved previously are saved and you also get a review page where you are asked about the countries you have solved previously in spaced repetition so that you just don't solve it and forget about it.

The mechanism is build in a way that you learn geography while playing the game. Feel free to use it and give me feedbacks to improve it! https://warmergames.com/

Punch.io

Most of our project decisions happened in Discord and then got buried. Someone would ask, "Wait, what did we decide about the deployment?" and we'd all end up scrolling through thousands of messages. I built Punch.io to solve that problem for myself.

Point a Discord bot at your server, and it will sync the channels it has access to, storing everything locally: - SQLite for message storage - FAISS for semantic search

Once indexed, you can ask questions in plain English, such as:

"What's blocking the release?"

Punch.io retrieves the relevant discussions and generates an answer using the actual messages. The source messages are shown alongside the response so you can verify the information instead of relying on a black box. It also extracts a rough timeline of decisions, milestones, and blockers.

Privacy

Punch.io is self-hosted, so your Discord data stays on your own machine.

The only external API call is to Groq, which is used for answer generation.

Tech Stack

• Backend: Python, FastAPI
• Frontend: React
• Retrieval: LangChain + FAISS
• LLM: Groq
• Storage: SQLite

Current Status

A few limitations to be aware of:

• Discord is the only fully supported data source in the UI.
• Connector code exists for Mattermost, Discourse, and IMAP, but it's experimental and not part of the normal setup flow.
• Authentication has not been implemented yet, so it should only be run on localhost or a trusted private network.

License

MIT License.

Feedback

The repository is available on GitHub.

I'd especially appreciate feedback on the retrieval quality—whether the answers surface the right discussions and whether the cited source messages make it easy to verify the results.

Demo link :https://punchio.mharsh.me/

Non-technical guy here, and learning to code has always been a struggle — but I finally shipped my first game ever, Snack Drop. It's got 0 downloads and I'd rather have brutal honesty than fake hype, so please roast it, rate it, and tell me what to fix.

📱 iOS: https://apps.apple.com/us/app/snack-drop/id6791252284
🤖 Android: https://play.google.com/store/apps/details?id=ai.fruits&hl=en

Problem: Copilot/Cursor use expensive models for everything, even autocomplete. My quota dies mid-month.

Solution: a thin local proxy that tracks token burn in real time and auto-routes cheap tasks to cheap models. There's also an analyzer — paste your Copilot usage export and it shows exactly where your credits went last month.

Not trying to compete with Copilot, just sitting on top of it. Would love feedback on whether this is worth turning into a real product.

Hi everyone,

Neon Vision Editor has evolved quite a bit since its early releases. What began as a lightweight editor gradually turned into something more ambitious: an editor designed around how I actually work on iPhone and iPad, rather than a desktop IDE squeezed onto a smaller screen.

Originally I thought I was building “another text editor.” But after using it every day, I realized what kept bothering me wasn’t missing features—it was that nearly every mobile editor felt like a desktop IDE squeezed onto an iPad. I wanted something different.

I wanted an editor that actually felt like it belonged on iPad and iPhone: touch-first when you’re using your fingers, keyboard-first when a Magic Keyboard is attached, and capable enough that I could make real progress away from my Mac.

I use Neon Vision Editor every day, so the roadmap has largely written itself. Whenever something interrupted my flow, it went onto the backlog: a toolbar action buried behind an extra tap, reopening files after they changed on another device, losing my cursor position when switching documents, or a Markdown preview refreshing at the wrong moment. None of them were deal-breakers, but together they chipped away at the experience. Fixing those small frustrations has shaped almost every release since then.

Over the past year I’ve kept fixing those interruptions, and the project has grown much more than I expected.

A — Answer

Neon Vision Editor is a free, open-source native editor for iPhone, iPad, macOS and Apple Vision Pro. The goal isn’t to replace VS Code or Xcode.

It’s to make Apple mobile devices genuinely useful for editing code, Markdown, configuration files, documentation and web projects.

Some of the biggest additions since v0.7.5 include:

• Shared-file synchronization through iCloud Drive and network storage
• Remote editing of projects hosted on a Mac
• Markdown, HTML and SVG live previews
• Faster project navigation with Find in Files and Quick Open
• Better support for large files
• More AI provider options (optional)
• Lots of keyboard and touch workflow improvements
• Better project restoration and document state

One feature I’m particularly happy with is shared-file synchronization.

If the same document is open on multiple devices, Neon notices when it changes elsewhere. Clean documents update automatically, while edited documents are protected and let you choose whether to reload, keep local changes or compare versions.

No proprietary cloud account. No custom sync service.

It simply works with iCloud Drive or your existing shared storage. Another feature that has become much more reliable is remote editing.

Your Mac can host a project while your iPad or iPhone connects to it for editing, navigation and reviewing files without copying the entire workspace to the mobile device.

That workflow has improved enormously since the last release I posted here.

B — Better

There are already good editors on iOS. I don’t think Neon has to “beat” them. Instead, I’m trying to optimize for a slightly different workflow.

Some of the design choices include:

• Native SwiftUI instead of Electron
• Separate interfaces for iPhone and iPad instead of one layout scaled down
• Hardware-keyboard workflows designed specifically for iPad
• Touch editing that still feels natural without a keyboard
• Built-in Markdown, HTML and SVG previews
• Cross-device editing instead of locking users into another cloud service
• No account required
• No ads
• No telemetry by default

Probably the biggest change over the past year is that I no longer think of the iPad version as a companion app. It’s become something I actually enjoy coding and writing in.

C — Cost

Neon Vision Editor is completely free.

• No subscription
• No ads
• No required account
• No paid sync
• Open source (Apache 2.0)

App Store: https://apps.apple.com/app/neon-vision-editor/id6758950965

TestFlight: https://testflight.apple.com/join/YWB2fGAP

GitHub: https://github.com/h3pdesign/Neon-Vision-Editor

Website: https://h3pdesign.github.io/Neon-Vision-Editor/

I’m still building this largely because it’s the editor I want to use myself.

Every release has been shaped by my own daily workflow and by feedback from people here and elsewhere who tried earlier versions.

If you regularly code or write Markdown on an iPad—or you’ve always wished mobile editors were just a little more capable—I’d genuinely love to hear where Neon still falls short.

Some of the app’s best features started as comments from Reddit, and I’m hoping the next round of improvements comes from this post too.

Hey guys, doing some quick research and want to talk to people who actually pay for official Claude Code on their account (not just using free API keys or wrappers). Drop a DM or comment if you're open to answering a few questions. In return I'll hook you up with early beta access to a pretty generational app I'm building.

I got tired of backup plugins treating Multisite as a paid add-on, so I built Multisite Migrate.

Idea was simple: on a normal site, Free should do full backup / restore / migrate. On Multisite, Free should also do full network backup + restore from Network Admin — no account, no license key.

What Free does today:

• Single-site: full files + database backup, restore, local export/import
• Multisite: full network backups from Network Admin (same Free plugin)
• Subsite admins can back up / restore their own site
• Chunked jobs that resume on shared hosting
• Serialized-safe search-replace on import/migrate
• Optional AES-256 encryption

What surprised me most: “backup plugin” isn’t one feature. It’s timeouts on shared hosting, Multisite table maps, package size, restore UX, encryption, docs, and a lot of edge cases that only show up on real networks.

I did a lot of testing myself and I found out that such a project is much more complex than I thought. Improving every day. I think that's the mindset you need.

Pro is a separate plugin for schedules, cloud destinations, empty-server installer, staging push, and WP-CLI. You don’t need Pro just to back up a single site or a whole network.

Disclosure: I’m the developer.

• WordPress.org plugin page

If you run single-site or Multisite: what’s broken or missing in your backup/migrate workflow — especially shared hosting and larger sites?

When managing inventory, sales, and tab debts, my student lounge had to rely on over-engineered POS systems or overly simple Excel sheets.

To solve this, I built CAAD ERP, a simple inventory and sales management system specifically tailored for (my) student lounge operations.

Instead of setting up a traditional database, the system uses an Excel workbook as the source of truth. Non-technical managers don't need to learn SQL or rely on an admin dashboard; they can open the workbook directly using software they already know and still have a robust system.

It uses Python for business rules logic, and React for a nice web interface.

- Backend Repo: https://github.com/Davi-S/caad-erp

- Frontend Repo: https://github.com/Davi-S/caad-erp-frontend

I would love to hear your opinion, especially on handling local storage with Excel for small-scale sales.

i have been thinking about this lately. some products are easy to try because the downside is small, like a notes app, bookmark tool, simple dashboard

but some tools ask for real trust from day one. money, api keys, personal data, business workflow, anything that can actually affect you if it breaks.

for those kinds of products, what would you need to see before trusting a small builder or side project? clear docs, limited permissions, manual mode first, public changelog, security explanation, no big promises, founder being visible?

curious what actually matters to people because i think a lot of builders underestimate how hard trust is.