PMs, designers, and backend engineers on our team often needed to check a staging build. Sometimes they wanted to verify a layout, sometimes reproduce a bug, or just confirm that an API change behaved the way they expected.

Sending the build wasn't the hard part.

Actually running it was.

Most people didn't have Xcode or Android Studio set up, and asking them to install everything just to check one build wasn't realistic. The alternative was usually asking a mobile developer to install the app or share their screen, which happened more often than we'd have liked.

We looked at services like Appetize and BrowserStack, but they didn't really fit how we work. We already had Macs available internally, and we weren't comfortable uploading app binaries to an external service just so teammates could review a staging build.

So I started building an open-source tool that runs iOS simulators and Android emulators on a Mac and streams them to the browser.

The idea wasn't to replace TestFlight or Appetize. I just wanted an easier way for teammates to review staging builds without needing a mobile development setup.

It's still early (v0.x), but building it has taken me into a lot of areas I hadn't worked on before—video streaming, low-latency input forwarding, simulator orchestration, and React Native QA workflows.

I'm curious how other React Native teams handle this.

How do non-mobile developers on your team review staging builds?

• TestFlight?
• Internal APKs?
• BrowserStack or Appetize?
• Something else?

If you're interested, here's the project:

https://github.com/jo-duchan/tapflow

Last month I posted about how much unplanned work gets absorbed into engineering sprints.

The post got more than 2,000 upvotes and ended up being the #1 post here for two days.

GitHub: https://github.com/Meridiona/meridian

But more importantly, the discussion made us dig deeper.

We started looking at why this happens, where all that invisible work goes, and how much it actually affects developers and engineering teams.

That eventually led us to build Meridian, an open-source developer tool focused on making a real difference to how developers understand and manage this unplanned work.

We’re open-sourcing it because we want developers to be able to look under the hood, challenge our approach, contribute, and help shape where it goes next.

If you’re a developer who has dealt with this problem, I’d genuinely like to hear what we’re missing and what you’d want a tool like this to do.

I originally started an early version in Wails, but eventually scrapped it and rebuilt the project from scratch with Tauri. The current version has been in serious development for a little over two months, and I just released v0.9.3.

The idea came from getting tired of the same problem with Git clients: they're great for Git, but as soon as I need to open a PR, check CI, review code, or look at an issue, I'm back in the browser.

GitDesktop is built around keeping that workflow in one application. It supports GitHub, GitLab, and Bitbucket, with pull requests, code reviews, issues, discussions, CI, releases, worktrees, interactive rebase, and other Git operations.

AI is an optional part of the workflow. It supports providers including OpenAI, Anthropic, Google, OpenRouter, and Ollama, as well as local/CLI agents. You can bring your own keys or run models locally. If you don't want AI at all, you can hide every AI feature.

The project is licensed under Apache-2.0.

GitHub: https://github.com/theBGuy/GitDesktop

Website: https://gitdesktop.app

I'd especially like feedback from other FOSS developers. What do you think is missing from the current Git client experience, or what would make you consider switching from your current Git client?

Website: https://NoSignups.net GitHub: https://github.com/BraveOPotato/FckSignups

Genuinely didn't expect it to blow up this much. I compiled videos from some of the creators who made videos about it here and honestly it makes me so happy!

The website is a directory of no-signup open-source tools you can use immediately in your browser. None of the tools are mine, I just collected them and made them searchable.

I have a few things cooking in the oven for the website, and here's some of them:

• I looked up how to do RSS (seems like it's just a simple file I need to provide at /rss.xml) and hopefully I'll have it available for the users to come back and discover more open-source tools.

• I plan on adding a change log so that users can come back and explore the newer found/added tools.

• I plan on adding a sorting drop-down so that users can explore at their leisure.

What I've already done:

• Thanks to the GitHub user Moamal-2000, the accessibility of the website was greatly improved! I mean by a mile! Appreciate all his work!

• Included some SEO metadata tags for search engines. I didn't even know about JSON-LD before I started this.

• Significantly improved the search so that searching video edit shows video-editor and edit video entries.

• Kept adding entries that match the criterias. Although, slowing down a bit. I'm employing whatever in my disposal to dig for more tools, and hopefully some more will turn up.

We've also been collecting some tool suggestions from users about what tools they'd like added. The top ones so far are:

• A tool to generate AI videos (obviously insanely impractical given the criterias the tools have to abide by, if not downright impossible with current ML models).

• Something like CapCut Pro (or something like that?)

• AI Image generators (possible with WebGPU), but haven't found any open-source, in-browser, no-signup entries.

• and more found here

I just wanted to thank all the contributors who submitted PRs, tools, opened issues, and reported bugs. Hopefully average joes will learn about and use the website, and hopefully support the amazing people making all these wonderful open-source tools.

Peace & love

Hey! I've been working for a very early stage startup called Mulga. We've been continuously working on our flagship product, Spinifex, which recreates core AWS services such as EC2, EBS and S3, locally (and even air-gapped if you want/need!).

Have a poke around our GitHub: https://github.com/mulgadc/spinifex

Feedback/criticism welcome!

I have been building this on and off for a while and it is finally at the point where handing it to someone else is not embarrassing, so here it is.

Citadel is a desktop infinite canvas. You drag in images, GIFs, video, audio, 3D models and PDFs, write notes and text blocks beside them, and draw labelled connections between things. It is for work where the layout is the thinking: visual development, research, worldbuilding, study.

The reason I started it: I used PureRef for years for images and kept everything else somewhere else. Notes in one app, clips in another, code snippets in a third. I wanted one board that could hold all of it and still be searchable a month later.

Three things ended up mattering more than I expected:

Connections carry meaning. A thread between two items can be a source, a contradiction, a question, a proof, an echo of something elsewhere. The Index searches every board at once, including code card contents and connection labels. That is the part that makes it hold up past about fifty items.

Vision checks. Y redraws the whole board in greyscale, blurred for a squint test, or through three colourblindness simulations. Shift+M mirrors it, which is the old trick for catching drawing errors your eye has stopped seeing.

Undo and recording are the same event log, so you can scrub the board back through its own history and watch it assemble itself.

It is local-first in the boring literal sense. No account, no telemetry, no update check, no network request on launch at all. Fonts are bundled. Projects are JSON with relative asset paths, so nothing is trapped in a database you cannot read. MIT licensed.

Honest limits: Windows and Linux only (macOS runs from source but I cannot notarise it), builds are unsigned so SmartScreen will warn on first run, PDFs get a first-page preview rather than a real reader, and document import gives you the plain text, not the formatting.

Repo: https://github.com/kannibalk1w1/Citadel. Downloads and a version that runs in the browser: https://kannibalkwi.itch.io/citadel

Happy to answer anything. What I would most like to hear is where it falls over on large boards, because that is the part I cannot test properly on my own.

Some of you are one typo-fix away from your first PR. Some of you have 200 merged and a burnout story. Some of you only touched a repo because a CS assignment forced you to. All of you are valid, and I want to hear it.

I've been lurking on how wildly different everyone's open-source journey is, and it lowkey fascinates me. So here's a soft invite to trauma-dump (or brag) in the comments:

🔁 stuck in a dread while loop - u built something cool. Perfectionism kicks in. "Not ready, not good enough, the maintainers will laugh." It dies in your drafts.

born different / got lucky - For some, the first PR felt like finding your tribe. Never looked back.

📚 uni chore - For others it's just homework. A checkbox on the way to a job. No shame.

The point: whatever got you here: ego, curiosity, a degree, boredom; every contribution helps the community at a holistic level.* (the psychic damage on maintainers is a post for another day 🥲)

So tell me your story. Failure or W, I want it all >>

• fixed a typo, shipped a bug, or rewrote the whole codebase?
• one night stand as a contributor, or max-level maintainer drowning in AI-slop PRs?

Only positive v̶i̶b̶e̶z̶ (sorry, too AI), only positive context lol. Be real, be yourself.

‼️Contribution Guidelines: follow the IDFC principle:

• I Don't F*.ing Care: just be genuine and be you.

> P.S. total newbies, here's a quick glaze through on how FOSS collaboration actually works: > > awesome-contributing

Hey there!

Building synap.md — a self-hosted, Obsidian-style Markdown notes app. Notes stay plain \`.md\` files on your own disk, no lock-in. Web app (Nuxt) + a native Tauri/Rust desktop client that syncs against your own server, offline-capable.

Still WIP with rough edges, but usable — and I'd genuinely love contributors, especially if local-first sync or Rust interests you.

Repo: https://github.com/BungeeDEV/synap-monorepo (MIT)

I built Afterdark Studio 0.8.0-rc.1 Limited Beta for emerging rappers working with one computer and one microphone. It runs locally in a browser and includes two DJ decks, beat sequencing/piano roll, microphone recording, vocal-production tools, LUFS/true-peak metering, and synthetic acoustic rooms. No account, cloud AI, or API key is required.

Ready-to-test source and setup: https://github.com/seemorecodez/afterdark-studio

Current automated evidence: 111 tests passing and 646/646 interactive controls covered in the Edge UI audit. Honest limits: this is not yet a professional DAW or autonomous DJ; perceptual vocal features are experimental; the isolated drill pack remains disabled after failing its creative gate.

I would value hands-on reports covering: first-run setup, beat quality, microphone/recording workflow, DJ transitions, crashes, audio glitches, and performance. Please include OS, browser, audio interface, and reproducible steps. I am the project creator and am requesting critique, not stars or sales.

موقع للدعم النفسي والفضفضه بدون تسجيل دخول و بشكل مجهول ومجاني بشكل كامل وبدون اعلانات

https://feelbetterbot.com/

TL;DR: Curium v0.6.4 brings the first desktop pre-release for macOS, Windows, and Linux, a new web version, and several new features including Share to Curium, gallery scanning, batch QR generation with ZIP export, Wi-Fi password visibility, camera performance improvements, smoother animations, and more. Curium CLI, a Rust-based command-line version, is also in development, while an iOS app is planned. Download Curium from GitHub, or visit curium.design to automatically find the right build for your device.

Hi everyone!

Curium, a modern, feature-rich, ad-free, and privacy-first QR customizer, generator, and scanner, now has desktop releases for macOS, Windows, and Linux, along with updated Android, a web version so you can use Curium from anywhere regardless of your device, and a website to make installation and documentation easier for everyone.

What Release v0.6.4 brings

• First pre-release for desktop
• A web version, so you can access Curium from anywhere
• Batch generation: Generate multiple QR codes at once and export them together as a ZIP file
• Share to Curium: Send QR codes from other apps directly into Curium
• Gallery Scan: Pick an image from your gallery to scan or redesign it
• Wi-Fi password toggle: Tap the eye icon to show or hide your password
• Camera performance improvements
• Smoother animations throughout the app
• And many other quality-of-life improvements

You can download Curium from the GitHub Releases. If you're confused about which build is right for your device, visit the Curium Website. It will automatically detect your device, suggest a compatible binary to download, and show you the installation steps.

You can also visit the download page to browse all available binaries and downloads. It will show a checkmark next to the build that matches your device.

For Android, if you accidentally download the wrong build, you can always install the universal APK, or check your device's supported architecture through other means before downloading the appropriate build.

For Linux, you can run:

curl -fsSL https://curium.design/install.sh | sh -s --

until Tauri fixes the .AppImage issue or I publish Curium to various Linux package managers. If you run into installation issues, check the README for troubleshooting steps. If you'd rather not install anything, the web version is always available at app.curium.design

Curium Web: app.curium.design
Get Curium from the website: curium.design
Get Curium from GitHub: github.com/nylxar/curium/releases
Support development: curium.design/sponsor

If you're facing any problems, you can create an issue on GitHub, reply here, or email me at nylxar@curium.design

Curium Desktop releases are still in beta, so expect a few things to break or remain unpolished.

I'm also working on Curium CLI, a Rust-based command-line version of Curium, which is currently in development. An iOS app is also planned and will be released as soon as I can gather the funds needed for Apple App Store enrollment and distribution.

A lot of effort is going into Curium with pure intention, and I hope you all like it! :)

DISCLAIMER: AI WAS HEAVILY USED, THIS IS ESSENTIALY VIBECODED

Tbh, I will start by saying that this is not finished, and it is still mostly a demo. However, I will continue building on it.

Anyways, what is it then? Well its uhh \*drumwirl\*

yaysafe

Yaysafe is used to check yay pkgbuilds, both via standardized things like "download russian virus not good (random curl requests for instance) and via LLM

Basically just:

yaysafe -S pkg

If I can get this working reliably, I would say its very useful because it might help people to look through pkgbuild quicker, and even as it is rn its useful, atleast for me.

Anyone mind taking a look? [github.com/crsgmi/yaysafe](http://github.com/crsgmi/yaysafe)

Please tell me if I have done something wrong or if it can be improved!

Hello everybody,

I built bulletinbored, a minimal and extensible forum software written in pure PHP with zero dependencies.

No Composer, no Docker, no Node, no framework. Just upload the files to any PHP 8.x server and it works on any web hosting, also shared and cheap ones.

Key points:

• SQLite by default (MySQL also supported)
• Web installer
• Plugin system with hooks
• Theme system
• Admin panel, user management, avatars, moderation
• Built-in localization
• Automatic update checks
• License: 0BSD

Repo: https://github.com/bulletinbored/bulletinbored-core

Website: https://www.bulletinbored.net

Docs: https://docs.bulletinbored.net

Because the development is still in early stage, I’m looking for any kind of feedback. Feel free to write suggestions, criticisms or slatings.

Happy to answer questions and open to contributions.

Thanks!

Hey,

I've been working on this for a while and thought I'd share it here.

It's called PkgLift and basically, I wanted an easier way to deal with moving older Xcode projects from CocoaPods to Swift Package-manager.

I know you can obviously do this manually but I didn't really like the idea of going through everything by hand, especially on projects with a many dependencies!

The thing I was worried about when building it was making a tool that just changes a bunch of stuff and assumes it worked. So PkgLift doesn't really work like that.

You first run:

pkglift analyze
pkglift plan

and it tries to work out what it actually knows how to migrate.

If it isn't sure about something it just leaves it alone instead of trying to guess.

Then you can check the plan yourself before actually changing anything.

If it looks good:

pkglift migrate --apply
pod install
pkglift verify

That's pretty much the idea.

It is still early and I'm sure there are plenty of CocoaPods setups that I haven't thought about yet, which is actually one of the reasons I'm posting it here.

You can install it with:

brew install Alexsvensson99/tap/pkglift

Repo:
https://github.com/Alexsvensson99/PkgLift

If anyone has an old CocoaPods project lying around and wants to try it, I'd be interested to know what happens. Especially if it fails on something weird :)

Hi everyone,

I wanted to share OpenChoreo, an open-source internal developer platform built for Kubernetes. It is also a CNCF Sandbox project.

The goal of OpenChoreo is to bring the main pieces needed for building an internal developer platform into one place, including a developer portal, CI/CD, GitOps, observability, and higher-level abstractions over Kubernetes.

The project is actively growing, and contributions from the community are very welcome. You do not necessarily have to contribute a major feature either. There are opportunities to:

• Work on Kubernetes and cloud-native features
• Improve documentation and examples
• Test the platform and report issues
• Contribute to the Backstage-based developer portal
• Suggest integrations, features, or improvements
• Help with community content and discussions

This could be a good project for Sri Lankan developers who are learning Kubernetes, Go, platform engineering, DevOps, or open-source contribution and want to gain experience by working on a real CNCF project.

Have a look at the project, try running it locally, and share your feedback. Contributions, questions, and ideas are all welcome.

GitHub: https://github.com/openchoreo/openchoreo
Thank you