Question for drone mapping / LiDAR folks: is there a need for a fast offline LAS/LAZ point-cloud viewer?

I’m a solo Mac/iOS developer and I’ve been experimenting with a native Apple Silicon point-cloud renderer. The basic idea would not be another full processing suite like Pix4D, DroneDeploy, CloudCompare, etc.

The idea is smaller:

A native iPad/Mac app where you can open a large LAS/LAZ point cloud locally, inspect it smoothly, maybe measure basic distances/elevation, save views, and export a quick client walkthrough video — without uploading the file or needing internet on-site.

The use case I’m trying to validate is:

• check a scan before leaving a site
• review large point clouds offline
• show a client a clean flythrough
• avoid fighting a heavy desktop/web viewer just to inspect/share the data

I’m not a surveyor, so I’m not pretending this would replace real survey/CAD workflows. I’m trying to figure out whether a focused “field viewer / client walkthrough” tool would actually be useful or if existing tools already solve this well enough.

A few questions:

1. Do you currently open LAS/LAZ point clouds in the field?
2. What do you use now?
3. What annoys you about the current workflow?
4. Would offline iPad/Mac viewing matter?
5. Would simple measurement + flythrough export be useful, or is that not enough?
6. Would anyone be willing to test an early build with a real file?

Brutal feedback is welcome. I’d rather find out now if this is useless before I build the wrong thing.

Hey everyone! I wanted to share something I've been building called Locker Drop.

I needed a way to send big files without paying a premium or jumping through hoops, so I built it.

Locker Drop is end-to-end encrypted right in your browser (works in Safari, Chrome, etc.). The part I'm proud of is the architecture: the decryption key lives only in the link fragment — it literally never touches our database or servers. We can't read your files, recover them, or hand them over. Once the file is downloaded (or the timer runs out), the encrypted payload is permanently purged.

For context: WeTransfer caps you at 2GB and isn't end-to-end encrypted. MASV charges around $1,250 to move 5TB. Locker Drop has no artificial caps, is truly private, and costs a few bucks.

TL;DR:

- True zero-knowledge (libsodium / XChaCha20-Poly1305 / Curve25519)

- No artificial size caps — up to 5TB today, larger on request

- No account or registration for anyone (sender or recipient)

- Self-destructs after reading

Pricing (I tried to keep it honest and affordable — I know the struggle is real):

- Up to 5 GB: $2.99

- Up to 100 GB: $8.99

- Up to 1 TB: $24.99

- Up to 5 TB: $79.00

Anything bigger than 5TB I haven't priced yet — if you need it, drop a comment and we'll figure it out.

https://preview.redd.it/5wo0v1m8fq9h1.png?width=2540&format=png&auto=webp&s=0980876a13a716e5365e4be1c875e7d2b7de0912

I'm handing out free codes so people can test it. My only ask: if you like it, share drop.inbox.locker with anyone who might use it.

Promo code: LOCKERLAUNCH

(1 GB per file, 100 uses. Enter it ON THE WEBSITE in the "Have a promo code?" box — NOT in the Polar checkout window.)

Site: https://drop.inbox.locker

Would love for you to tear it apart — the architecture, the crypto, the UI, whatever. Honest feedback welcome. I really need a win, and I'm hoping this is it. Thanks everyone!

Thanks,

Nathan

Hey everyone — wanted to share something I've been building called Locker Drop.

I needed a way to send big files without paying a premium or jumping through hoops, so I built it.

Locker Drop is end-to-end encrypted right in your browser (works in Safari, Chrome, etc.). The part I'm proud of is the architecture: the decryption key lives only in the link fragment, it literally never touches our database or servers. We can't read your files, recover them, or hand them over. Once the file is downloaded (or the timer runs out), the encrypted payload is permanently purged.

For context: WeTransfer caps you at 2GB and isn't end-to-end encrypted. MASV charges around $1,250 to move 5TB. Locker Drop has no artificial caps, is truly private, and costs a few bucks.

TL;DR:

- True zero-knowledge (libsodium / XChaCha20-Poly1305 / Curve25519)

- No artificial size caps — up to 5TB today, larger on request

- No account or registration for anyone (sender or recipient)

- Self-destructs after reading

Pricing (I tried to keep it honest and affordable — I know the struggle is real):

- Up to 5 GB: $2.99

- Up to 100 GB: $8.99

- Up to 1 TB: $24.99

- Up to 5 TB: $79.00

Anything bigger than 5TB I haven't priced yet — if you need it, drop a comment and we'll figure it out.

I'm handing out free codes so people can test it. My only ask: if you like it, share drop.inbox.locker with anyone who might use it.

Promo code: LOCKERLAUNCH

(1 GB per file, 100 uses. Enter it ON THE WEBSITE in the "Have a promo code? box NOT the in the polar checkout window.)

Site: https://drop.inbox.locker

Would love for you to tear it apart — the architecture, the crypto, the UI, whatever, all welcome.

I really need a win, and I'm hoping this is it. Thanks everyone!

drop.inbox.locker

I've been vibe coding for a 7 months now, and built multiple projects at the same time.... anyone else loose track of important things lol! I'm a little embarrassed to say I just recently figured out how to just bam get right back into the session with nothing missed or forgotten from last time.

If you use Claude Code on a long project, you know the pain: every new session it has no idea what you were doing, so you re-explain everything. I set up a little file that fixes this. Double-click it and Claude launches already caught up. Here is the whole setup.

The Idea

Two pieces working together:

1. Memory files Claude keeps in its project memory folder (a short index plus a "handoff" note with the current state and how to ship).
2. A double-clickable .command file that opens your project and launches Claude with a prompt telling it to read those notes first.

Step 1: Have Claude keep notes

Just tell Claude, in plain language:

>

Claude writes these to its own memory folder for that project. You do not manage them.

Step 2: Make the resume file

Create a file in your home folder (not Downloads, it can have permission issues) called myproject-resume.command.

Paste this and change the two marked spots:

Bash

#!/bin/bash
REPO="/Users/YOURNAME/path/to/your/project"   # <-- change this

clear
cd "$REPO" || { echo "Cannot reach repo"; read -n 1; exit 1; }

# raise the file limit so Claude does not bail on launch
CUR="$(ulimit -Sn)"
if [ "$CUR" != "unlimited" ] && [ "$CUR" -lt 10240 ] 2>/dev/null; then
  ulimit -n 10240 2>/dev/null || true
fi

echo "Working in: $REPO"
echo "Latest commits:"
git log --oneline -3 2>/dev/null | sed 's/^/   /'
echo
echo "Launching Claude..."

claude "PASTE YOUR BRIEFING PROMPT HERE"     # <-- change this

Then make it double-clickable. In Terminal, run:

Bash

chmod +x ~/myproject-resume.command

Now double-clicking it opens your project and starts Claude.

Step 3: The briefing prompt

This is the text that goes inside the claude "..." line. The trick is to make the very first instruction "read your own notes." A good template:

>

Fill the brackets with your real stuff. Mine, for example, tells it how I deploy, which folders to leave alone, and that database changes have to be done a specific way.

Why it works

The memory notes hold the knowledge. The .command file is just a fast way to drop Claude back into that knowledge without you typing anything. New session, one double-click, and it already knows your deploy process, your rules, and where you stopped.

💡 Tip: Ask Claude to update the handoff note at the end of each session. Then the next resume is always current.

I hope this helps at least one person!

Hi everyone,

I'm Nathan, a solo dev, and I wanted to share something I've been building natively for macOS: Screen Stage.

It’s a 4MB custom Metal engine designed to solve two massive pain points I kept hitting: making production-grade App Store screenshots/videos without messing around in After Effects, and streaming live simulators/code into OBS without killing my frame rate.

Because it’s built natively for Apple Silicon, it utilizes zero-copy memory sharing. You can map your live Xcode simulator, a window, or a game onto a photoreal 3D device at up to 120fps with zero lag.

What it actually does:

• App Store Sets in One Shot: It batch-exports every exact pixel size Apple requires. You change a feature, drop the new screenshot in, and it re-renders the whole localized set.
• On-Device AI Scene Director & Captions: Uses Apple’s local models to write and translate captions, or change the scene lighting/weather via text prompt. 100% local, nothing hits the cloud.
• Live OBS Streaming: Publishes a built-in source over Syphon. Turn on "Control" and you can actually tap/scroll the 3D device to drive your live running app during a demo or stream.

It’s currently in private alpha. I really wanted to build something fast, light, and entirely local—no web wrappers, no Electron, and no cloud rendering queues.

I'd love to hear your thoughts on the workflow or any features you think are missing for optimizing App Store assets!

Check it out here: Screenstage.io

Let me know what you think!

https://preview.redd.it/icryj7l0jf8h1.png?width=2576&format=png&auto=webp&s=559efc093746e3a32d2f5bdb93e25d8160bfc1f3

Hey all, solo dev here. I've been building a native Mac app with a real time Metal engine (no cloud, no render wait), and I'm adding a live mode for streamers.

The idea: capture your game or app window live, drop it onto a 3D device or screen inside a cinematic scene (rain, neon, motion blur, the works), and pipe that straight into OBS as a source. So your stream looks like a mini keynote instead of a flat window capture, all rendered live on your machine at 60 to 120fps.

It's early and I want to build it right, so I'm looking for a few Mac streamers to test it and tell me what would actually be useful. Free for testers.

If you stream on a Mac and this sounds cool, drop a comment or DM and I'll get you in.

Thanks

fob.sh/dolly

Hi, I'm Nathan. Started vibe coding in October 2025, and my first App Store screenshot submission was a disaster — wrong pixel sizes, rejected uploads, hours gone.

So I built the thing I wished existed. Drag a screenshot or screen recording in, it lands on a 3D iPhone/iPad/MacBook in a little studio — real lighting, reflections, dust in the air. Drag text right onto the shot. One click exports PNGs at the exact sizes Apple accepts (all 5 at once), or a 4K/60 video of a camera move. There's also a cinema mode that throws your demo onto a giant theater screen, which is honestly just fun.

Fun detail: the rendering engine started life as a LiDAR point-cloud engine I built for a search-and-rescue app. Everything's native Metal, runs locally, exports in seconds — no cloud.

https://preview.redd.it/na1jfy6btd6h1.png?width=2688&format=png&auto=webp&s=1d5d4d586ba02cdbfe1a697c48dced8ec0f1dd44

Looking for 5 people with Apple Silicon Macs to break it tonight and tell me what's confusing. DM me and I'll send a download link and an access key. Happy to answer anything about how it's built.

https://preview.redd.it/65hoiwcq3d6h1.png?width=2688&format=png&auto=webp&s=708ec0910dfbdd272c1812a0de91cf63f20d8138

Hi, I'm Nathan. Started vibe coding in October 2025, and my first App Store screenshot submission was a disaster — wrong pixel sizes, rejected uploads, hours gone.

So I built the thing I wished existed. Drag a screenshot or screen recording in, it lands on a 3D iPhone/iPad/MacBook in a little studio — real lighting, reflections, dust in the air. Drag text right onto the shot. One click exports PNGs at the exact sizes Apple accepts (all 5 at once), or a 4K/60 video of a camera move. There's also a cinema mode that throws your demo onto a giant theater screen, which is honestly just fun.

Fun detail: the rendering engine started life as a LiDAR point-cloud engine I built for a search-and-rescue app. Everything's native Metal, runs locally, exports in seconds — no cloud.

Looking for 5 people with Apple Silicon Macs to break it tonight and tell me what's confusing. DM me and I'll send a download link and an access key. Happy to answer anything about how it's built.

https://preview.redd.it/68mce17n2d6h1.png?width=2688&format=png&auto=webp&s=d0ff990b0908b239a83562b66c21da07d1607e3b

Hi, I'm Nathan. Started vibe coding in October 2025, and my first App Store screenshot submission was a disaster! Typically the wrong pixel sizes, rejected uploads, hours gone.

So I built the thing I wished existed. Drag a screenshot or screen recording in, it lands on a 3D iPhone/iPad/MacBook in a little studio — real lighting, reflections, dust in the air. Drag text right onto the shot. One click exports PNGs at the exact sizes Apple accepts (all 5 at once), or a 4K/60 video of a camera move. There's also a cinema mode that throws your demo onto a giant theater screen, which is honestly just fun.

Fun detail: the rendering engine started life as a LiDAR point-cloud engine I built for a search-and-rescue app. Everything's native Metal, runs locally, exports in seconds , no cloud.

Looking for 5 people with Apple Silicon Macs to break it tonight and tell me what's confusing. DM me and I'll send a download link and an access key. Happy to answer anything about how it's built.

Hey everyone,

I've been leaning heavily into vibe coding lately, running tools like Claude Code and various CLI agents to spin up features fast. But I kept hitting this massive wall: the AI context tax.

If I spend a bunch of tokens getting Claude caught up on a bug, it gives me a brilliant fix. Then an hour later, I open ChatGPT or hop into another terminal session to look at a related issue, and the context is completely gone. I find myself constantly copy-pasting the same 4 files, re-running the same explanations, and paying for the exact same tokens all over again just to get the next tool caught up.

There was no shared tissue between my project files and the different AI tools I was throwing at them.

So I built Fob. It is a local-first workspace that acts as a continuity layer sitting right between your code and your agents.

How it works under the hood:

• It runs entirely locally on your machine (binds to 127.0.0.1). No third-party cloud database syncing your private code.
• It stores facts, pins, handoffs, and conflict resolutions in a local folder right inside your project workspace.
• It exposes a headless local API and an MCP server, so you can pull your saved project context straight into whatever compatible AI workflow or tool you want to use next.
• It adds a local approval surface so you can visually review diffs before letting an agent blindly run git commands.

I also built an open-source companion CLI tool called CLOAK that comes with it. It does AST-based obfuscation and redaction locally, so you don't accidentally leak proprietary strings or keys to public models when you are moving fast.

I just put up a live web demo page that shows the local dashboard running against a safe mock project structure here: https://fob.sh/demo

I'm trying to figure out how to make agent handoffs smoother when switching tasks. How are you guys managing context drift when you're jumping between different tools and chats? Would love to get some feedback on the setup.

Hi everyone,

I've been in this group for awhile and would love to show off my recent build.

I started vibe coding back in October 2025, my first project was a budget app (with iCloud sharing) I tore off something really advanced for a first project, since then the level of apps and other projects have just gone crazy! I've used custom tools to help me work faster and of course AI. Happy to discuss and talk about how any of these work.

I would love some feedback on this app and any advice from fellow people in this group.

I’m happy to say BRYKK is finally live on the App Store.

Right now it is iOS only, so it works on iPhone, Apple Watch, Apple TV, widgets, and Live Activities. Android is next. I’ll be starting the Android version soon.

What does BRYKK do?

BRYKK helps families know everyone is okay without making it feel creepy or like a surveillance app.

You can:

- See your family on a live map

- Get notified when someone arrives or leaves places like Home, Work, School, Nana’s, daycare, etc.

- Follow a drive in real time

- See speed and movement status

- Use SOS and crash/impact safety features

- Message your family

- Use Apple Watch and Apple TV as family safety screens

- Build Safety Cards with important emergency info, notes, medical details, and things someone may need to know quickly if something happens

Saved Places are a big part of BRYKK. These are places that matter to your family, like Home, Work, School, grandparents, sports fields, daycare, or anywhere you want arrival/departure alerts.

Privacy matters:

I built BRYKK because I wanted family safety without the creepy feeling. I’m not selling your family’s location data. I’m not building an ad business around where your kids go. BRYKK is built around family safety, not tracking people for profit.

How is it different than Life360?

I’m not trying to build another app that feels like it’s watching everyone all day. BRYKK is more about “is everyone okay?” and “did they make it there?” It’s built around family safety, saved places, real-time drives, emergency moments, and a calmer family map.

I’ve also spent a lot of time trying to make BRYKK smart about battery and real life use. It sleeps when someone is safely at a saved place, wakes up during drives, handles weak signal areas better, and tries not to burn battery just to make a dot move on a map.

It is also Apple-first, with Apple Watch, Apple TV, widgets, and Live Activities actually being part of the experience.

Pricing:

BRYKK Safe is free and includes:

- Up to 4 family members

- Up to 2 saved places

- Family map

- Arrival/departure alerts

- Messaging

- SOS

- Impact/crash detection

BRYKK Life is optional and covers the whole BRYKK family:

- Up to 10 family members

- More saved places

- Trip history

- Translation

- More family tools and premium features

BRYKK Life is $6.99/month or $49.99/year, and only one person in your BRYKK family needs it. They do not have to be in your Apple Family Sharing plan.

If you’re willing to try it, I’d really appreciate the download, feedback, and any bug reports. I’m still actively improving it every day.

I’m also working on a public web dashboard and have room for a few families to test it. If you want access to that, let me know.

Download BRYKK Family Safety here:

https://apps.apple.com/us/app/brykk-family-safety/id6761343948

Here we go!

I'm currently going through the apple review stages, lets hope the 3rd review is all good finally lol!

But let me hear it, what was your biggest pain point or what did you learn from apple review that you wish you learned sooner.

Anyways keep on building!

I keep going back and forth on what to change or update for my portfolio site. Maybe I'm just never happy with the results. I'd love to see some inspiration from your current websites.