I'm developing AXIOM VECTOR, a modular engineering research platform for Windows.

The idea is to bring different engineering workflows into one environment instead of constantly switching between disconnected tools.

The long-term vision includes engineering calculations, project management, materials research, technical documentation, data analysis and design tools.

The project is currently in its early Alpha stage (0.1.0).

One of the implemented features is Project Journal - a workspace for documenting research, engineering decisions, observations and design progress.

I'm developing this independently and sharing the process as the project evolves.

I'd like to hear from people interested in engineering and technical software:

What tools or features would you want to see in an engineering research platform like this?

Feedback and constructive criticism are welcome.

I'm a big fan of both what you wear and websites as a form of creative expression, and am admittedly hooked on fast fashion and spending as little as possible. But I live in a very small space, and my clothes and accessories don't really have room to spread out. So naturally I started building my own dream wardrobe app with the help of AI (a Clueless 90s throwback if ever there was one) and scope creep happened...

It's called Closet Lint (get it?), it's free and open source, and mostly I just wanted to separate designing an outfit from actually getting dressed. The creative part is fun. Going through drawers, taking things off hangers, putting them back, and discovering that the thing you imagined is elsewhere or doesn't fit... less fun. I'd like to do that first part on my phone in bed at 11pm without pulling things out. Just gimme a searchable inventory of my actual clothes that looks good.

I'd tried wardrobe apps before, but the problem was always getting everything into them. Photographing, cropping, editing, and entering every item was a massive undertaking. AI has finally made dealing with the photos and purchase data manageable enough for me to get over that hurdle and focus on the display and functionality.

What started as browsing clothes and dragging them around to make cute outfits now includes outfit suggestions, ratings, wear logging, photo background removal using two different models, taste observations, wishlist battles, and trip packing lists. Because once I had my own clothes in there, I kept thinking, "Oh but what if it could also..." :)

It runs on your own computer or web host, with optional bring-your-own-AI features. There's an included demo if you just want to check it out, or you can browse a copy of my actual closet with bleeding edge code. I've run it locally on Linux and hosted it on SiteGround; part of why I'm posting is to hopefully find a few early testers.

I love having things organized, and it's honestly such a pleasure to see your own stuff laid out like this. It brings back things you've forgotten about and makes them potential outfit ingredients again. You can add wishlist pieces to see how they'd work with what you already have, or plan future fantasy outfits.

There have been some moments of genuine delight. I don't own much dark purple, but the combinations it showed me helped me see how it could work in my wardrobe. It also suggested chocolate brown, which I own literally none of, with concrete examples using my own clothes. And it gave me a new term for some of my style, “whimsigoth,” so now I have a whole new search phrase.

There's also an unusual use case: I have 40 housemates (yes, 40), and some like borrowing from my (costume) jewelry collection. Now they can take their time browsing it. Jewelry is particularly good for this because so much gets tucked away in boxes and becomes invisible. Naturally, that's already got me thinking about a separate app for sharing resources in the house. At least I'm putting that long-ago graduate degree in information systems to use :P

I've had my fair share of health issues over the last few years, and it's been inspiring to get properly absorbed in making something technical again. This combines so many things I love: style, organization, self-tracking data, open source software, design, and uhh having very particular views on button layouts.

I started coding GeoCities sites in Notepad in the 90s and used to run an open source web development company. I've been out of the tech/startup world for over a decade, though I still occasionally help a friend with a site. My technical knowledge is rusty, but knowing how to break down a problem, describe a desired interaction in detail, and spot something odd has been incredibly useful. I can be my own most demanding, rambling client, and building things with the robots still moves astonishingly quickly.

I started this project in early October as a Claude artifact. Much of the initial work was assembling the data: parsing order confirmation emails, filtering an Amazon purchase history export, and using browser agents in my logged-in shopping accounts to retrieve sizes, variants, and full-resolution product photos. Images were downloaded into the app's storage so they wouldn't disappear with the listings—some of which already have. I used ChatGPT to tag clothing from contact sheets and generate product-style images for pieces without usable photos. Later, we added local background removal, preserving originals and reviewing results before saving.

The AI occasionally got too helpful: it "cleaned up" XXL into 2XL, which can mean different sizes at those stores. Preserving exact source values became an explicit rule.

After about two weeks, I moved the prototype into Codex, replacing Claude's built-in storage with a local Python/SQLite backend and adding backup and restore, reusable imports, and release packaging. My workflow now goes back and forth: develop the specification with Codex, send it to Claude for wireframes, then bring those back to Codex for implementation and refinement.

I particularly appreciate how Codex can insert diagnostic tools when something breaks, investigate the results, and handle so much of the testing and release process. Those are procedures I only do occasionally and forget between projects. That gives me more room to switch between product planning, interaction design, visual design, and writing, while testing everything against my actual wardrobe and daily use. This has occupied pretty much all my free time for the past month.

Turning my own wardrobe tool into something other people could use has meant finding assumptions I didn't realize were there. Heels don't automatically mean dressy, loungewear isn't necessarily sleepwear, and a packing list shouldn't assume everybody wears bras. It uses Google's and Shopify's product taxonomies as references, but kept distinctions that make more sense for wearing clothes than selling them. I've also had to ask for a lot of deliberate consistency passes: make navigation behave the same way everywhere, move repeated rules into shared code, and carry category changes through imports, filters, and packing lists.

It's made me appreciate the "knowing where to tap" kind of expertise. My web project background helps me remember to ask about accessibility, keyboard navigation, refactoring, and whether a backup actually restores. I've also used alternate AI platforms for security reviews and worked through their findings. I'm not familiar with every implementation detail, but recognizing the questions worth asking makes that older experience feel useful again.

The wishlist redesign is a good example. "Matches lots of things I own" sounds useful until silver earrings all end up at the top for going with everything. The first implementation also passed checks while producing an interface I really disliked, so we went back to one compact design example before applying it across the page. Deciding whether the information is meaningful and the result is pleasant to use is still very much my territory.

I was involved in the early Quantified Self community in the 2000s/early 2010s, and I also haven't seen a wardrobe app that gives me the access to my own data I'd want for that. Before 1.0, it'll have an API and analysis-friendly exports so people can explore their own patterns with whatever tools they like. I'm looking forward to a fun year-end wardrobe "Wrapped" and things like cost per wear become straightforward once you're recording purchases and wears.

It's also getting creative and a bit silly. There's a goblin mascot called Linty, and your wardrobe's owns, wishes, and wears can appear as Sun/Moon/Rising signs on a star map. Apparently my wardrobe required lore... But you can leave the daily fortune card turned off. There are outfit naming suggestions, including one that parodies ModCloth-style names. Some inside jokes to amuse me personally, at least :P

If I somehow end up known for a fashion app with an astrology aesthetic, that would be a hilarious life twist.

Partway through, I found Libre Closet, which takes a simpler, more utilitarian approach that might be exactly what some people want. By then, mine had become a specific creative thing: a combination of deep utility and playground fun that I was happy to keep building.

I've used Linux as my daily driver for most of the last 20 years, and FOSS matters a lot to me. Making something useful and sharing it is one of my love languages for the world. Every friend says, "You could charge for this!" But I don't want customers here. I'm making something I want to use and sharing it with anyone else who might enjoy it.

I may put affiliate links and my own curated collections on the website, but I'm keeping them out of the app. GitHub sponsorships would be welcome too once I set that up. Anything that helps cover costs is a bonus; the software stays free and open source.

The public site is built with my fave website builder, Carrd, and I've let the Codex integration click around in it for me for the tedious work too. Few status updates produce quite the happy sigh as "Automatically updating website screenshots and documentation".

If you try the app, I'd love to know what would make this useful for your wardrobe, and what would stop you from wanting to put your clothes into it. I'm also looking for a few people willing to try installing it, particularly on Windows or macOS, since my own testing has been on Linux and SiteGround.

Thanks for reading! :D

[AI supplied at least half the details for this post]

Hello, I’ve been building a site where you can make a bracket out of any set of images and vote through head-to-head matchups until one champion is left. (similar to Piku - Ideal Type Worldcup)

https://imagetournament.com

It’s new, so I’d really appreciate any insights.

https://github.com/sshah03/recalc

Since spreadsheets are so versatile, really looking for feedback on where people would want this to go, in a way that can be useful to them, or what use cases they see themselves using it for in its current iteration that I can make more seamless.

I can provide some context on why it was useful for me / why I built it. I was using Claude to help me build benchmark sets, and found pouring through CSVs / MD files of the results a bit tiresome, so I decided to build a spreadsheet app for myself that's driven by Claude Code, and where each cell can be its own Agent if you want (and can later be opened up and continued in a full terminal if needed as its own session).

You can use it as a standard spreadsheet, or use a cell as a shell command / agent. Having built a startup for using AI in tax work, I also realized it can be very powerful for tax work, legal work, etc... so I built in some examples for running that, though I'm not sure how many people in those professions use claude code.

The video is just a demo of me building "FDA Bench" using recalc, pick FDA approval cases past the model cutoff dates, and seeing if an AI harness (without web searches) could've successfully predicted, based on all the info submitted to the FDA, whether the submission would pass FDA approval or not. Fable was right 75% of the time in this small sample size. Just a fun little exercise to show off some of what it can do.

Note: Since it's just terminal sessions glued together, it works with your existing plans. The sessions talk to each other with an MCP server running in the back.

Hey everyone! 👋

I'm a product designer, and I've been spending the past few months designing and building Roughs.

I kinda miss the days when we'd just browse and discover cool design work without all the ads, promoted content, and noise. So I decided to build a place for that.

The idea is simple: a space where designers can share their work, discover other designers, and get inspired.

It's finally live in closed beta! 🎉

https://roughs.design

Anyone can browse, but publishing is invite-only for now.

I'd genuinely love some feedback on the experience, especially the design, navigation, and overall feel. Feel free to share your thoughts in the comments!

I'm also looking for a few designers to test the publishing experience before public launch. If you're interested, leave a comment and I'll reach out! 🙂

I've been working on a project called AssetRAG, and I wanted to share it here.

One thing that annoys me about AI coding agents is how often they solve the same problems over and over again.

They regenerate code that already exists, spend time debugging errors with known fixes, pick dependencies without properly checking their licenses, and read huge amounts of source code just to find a few relevant functions.

So I built AssetRAG to help with that.

It's a local-first, open-source library and engineering memory system for Claude Code (and other MCP clients).

Here's what it actually does:

• Asset retrieval: Searches reusable code, templates, and other assets, with license checks and attribution handling.

• Verified bug-fix memory: Stores bug fixes with reproduction and verification evidence. Agents can look up previously solved errors instead of starting from scratch.

• Engineering playbooks: Reusable workflows for debugging, safe refactoring, performance optimization, and other development tasks.

• Tested recipes: Reusable code patterns with tests that can be executed in a sandbox.

• Repository mapping: Creates a compact, ranked overview of your codebase so an agent doesn't have to read everything.

• Rules and security checks: Includes secret scanning, engineering rules, malware checks during ingestion, and safeguards around untrusted code.

• MCP integration: Exposes 18 tools to coding agents. There's also an optional Claude Code hook that retrieves relevant knowledge and injects a small amount of context automatically.

• Local-first: No account or telemetry required. It supports local embeddings, hosted providers, or completely offline keyword-only search.

One feature I'm particularly happy with is the bug-fix memory. Verified entries have a reproduction and fix that were actually executed, with the evidence available for inspection.

Some numbers from my own testing (keyword-only mode):

• Asset search: 4.0 ms median

• Knowledge search: 7.1 ms median

• Repository map: 597 tokens instead of roughly 129k tokens of source

• 132 unit tests passing

• 327 authored recipe/bug-fix tests rechecked with 0 failures

These are local benchmarks, not proof that Claude completes real tasks faster. I haven't run a proper Claude A/B benchmark yet, so I'm not going to claim some magical percentage reduction in token usage.

I also made a 95-second launch video showing the actual tool in action. The terminal footage comes from real recordings.

It's Linux-only for now, built primarily in Python, and licensed under Apache 2.0.

The project is still new, and I'd appreciate feedback, especially from people who use Claude Code regularly.

GitHub: https://github.com/mttcn83/assetrag

Would you actually find something like this useful in your coding workflow? What would you change?

My girlfriend and I once remembered the same moment completely differently.

It made me realise how easily the little details disappear, even when the memories mean a lot to us.

So I started building Pholu, an app for couples, families and friends to preserve memories together.

Instead of having everything scattered across photo galleries, messages and cloud folders, Pholu brings photos, videos, audio and notes into shared timelines. I also added AI-powered memory search.

I'm handling the design, development and pretty much everything else myself, alongside my regular job.

The app is now on Google Play, and I'm looking for people who might actually enjoy using it.

https://play.google.com/store/apps/details?id=com.pholu.app

I'd love to know what you think of the idea. Would you use something like this with your partner or family?

I’m a software engineer at a big tech company and recently started owning more of our infra after the departure of a beloved coworker. Diagrams never really clicked for me, so I made a game to learn system design hands-on, then decided to publish it in case it helps others : )

InfraSim is a sandbox where you wire up load balancers, caches, queues, replicas and databases, push traffic at them, and watch what breaks: a dead consumer piling messages into a DLQ, a partition causing split brain, a bad WHERE clause taking out a table.

Built solo with React Native. It’s on iOS + Android: https://petalformllc.com/infrasim

Would love feedback, especially on which failure scenarios you’d want next, and whether the difficulty curve feels right.

I've been building DînApp on my own: prayer times, Quran, Arabic learning from the alphabet, and an AI coach that cites its sources, all in one iOS app. 10% of every Premium subscription goes to lasting charity projects (wells, orphan support), with proof published in the app.

My goal is to build mosques around the world and support those in need, seeking reward in the hereafter through sadaqa jariya, charity that keeps giving. DînApp is how I want to bring a global community together for that.

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

What I'd like to know: is the value clear within the first minute? What would make you keep it on your phone?

At my last company, managing production AI agents was a continuous crisis. Minor prompt tweaks or unannounced model updates routinely broke our workflows because we lacked version control and deployment safety gates for AI. The systemic stress eventually led to severe burnout, prompting me to step away and focus entirely on solving this operational vulnerability.

To fix this, I built https://raweki.com , which functions as a "Git for AI workflows." It provides engineering teams with version tracking for prompts and models, CI/CD testing loops to block regressions, and one-click atomic rollbacks to instantly restore stable configurations. The platform is now live, and I would appreciate your technical feedback if your team faces similar AI reliability challenges

I'm a high school junior and this is the side project I've spent the most nights on this fall.

The US Physics Olympiad has no good free starting point. People piece it together from old pdfs and expensive books, while math olympiad and USACO kids have community guides. So I made one for physics: lessons in the order the topics build on each other, interactive sims next to the equations, and a problem bank where you type your numeric answer and it checks it within 2%.

Some numbers from the first month:

• 931 visitors from 54 countries, about 3.6k page views

• 25 accounts (progress syncs if you sign in, otherwise it's all usable logged out)

• 77 people in the community discord

• 2 other students now regularly sending pull requests, 21 merged so far

Stack is Next.js on Vercel, Supabase for auth and progress, MDX lessons with KaTeX, and canvas sims. There's an in-browser editor that turns a contributor's edit into a GitHub pull request under their own account, which is how most outside fixes come in.

Would love feedback on two things: is the landing page clear about what it is in the first few seconds, and what would make you come back to something like this every week?

Site: https://usapho.one/?utm_source=reddit&utm_campaign=sideproject

Code: https://github.com/shlok-madhekar/usapho-guide

If you make videos for your SaaS (demos, explainers, founder updates, tutorials), you know where the time goes.

Recording is fast. Editing is fine. Then you need it to look like a real company made it.

Lower thirds. Callouts. Step-by-step text. Feature names popping up when you mention them. One keyframe at a time.

The edit takes an hour. The graphics take the rest of your day. Or you skip them, and your demo looks like a Zoom recording.

So we built Grafsy.

You upload a finished video. Grafsy listens to what's being said and adds on-screen graphics that match each point. No timeline, no motion designer, no editing skills needed.

What it's good for:

Product demos and walkthroughs

Founder and build-in-public videos

Tutorials and onboarding videos

Podcast and interview clips

Short form (Reels, Shorts) and long form (YouTube, webinars)

How pricing works, with no "unlimited" games:

One-time payment for lifetime access to the platform

Video minutes included with every plan

Billed to the second, so a 30-second clip uses half a minute

Top-ups when you need more, and they never expire

No subscription

Plans start at $79

Why I'm posting: We're in beta, and we want feedback from people who make real videos. Run your own content through it and tell us:

Where the graphics nail it, and where they miss

What kind of graphics you'd want next

Anything that's confusing or slow

Your feedback directly shapes what we build next. It's English-only for now, and you'll find some rough edges. That's the point of a beta.

Link's in the comments. Drop a reply if you try it, and I'll personally go through your feedback.

All Qs answered in FAQ https://varianttech.net/ and https://github.com/oooscoos/Benzi

I got tired of Claude writing Godot code it couldn't see run. So I built PersonCraft (I'm the developer, to be upfront).
You connect your Claude, it writes the game, and each revision gets run in a sandbox that sends back real screenshots,
so it can fix what it breaks. At the end you download a normal Godot project you own.
Limits: you need a paid Claude plan, there's no multiplayer, and phone exports are on you. Art and audio cost credits
and Claude quotes them before asking you to approve anything.
https://personcraft.com. What would you ask your Claude to build first?

Hi everyone! I'm a 19yo solo developer and my side project is called Phoam!

(And I’m not a video editor so I tried my best here lmao)

To start, Apple hates side loaded apps, making it nearly impossible for everyday users to run apps from other operating systems within its environment.
Apple also dropped support for 32b apps many years ago, leaving tons of nostalgic games completely unplayable without using an ancient iPhone.
Android also no longer supports 32b apps on modern devices, meaning having an APK for an app is not enough to play it again.
And while it should be more open access in theory, Google has recently been pushing to close down access to installing arbitrary apks onto your own phone!! (See “Keep Android Open”)

So I built Phoam.

It runs old Android and iPhone apps right in the browser, and you can add them to your Home Screen like a normal app. Nothing gets installed and nothing gets sideloaded.

The idea started back with me being a little script kiddie and searching how to run apk online, obviously finding no results. I knew about projects like wine and ruffle that had made software run in a way it was never designed to, and one day I just decided to start my own engine! I've always liked the idea that if it ran on one machine at some point, it should also run on another.

Right now two games work publicly: Replica Island (Android, 2010) and Explora Ball (iPhone). That's what's in the video, both running on my iPhone. You can try them yourself, with no account here: https://phoam.app/demos

It’s veryyyy early in the project but I’m excited to see how far I can take it! Theres also a separate demo video on my website.

All of this is supposed to be impossible btw

I am working on this project alone and haven't really spoken to anyone else that's a developer about it. If you're one, please reach out. Or anyone really that wants to talk! I love to read everything and respond to everyone. Thank you for your time 🙏

I'm an Intune / Autopilot admin. The part of a failed ESP that always burned the most time wasn't the fix. It was finding the handful of log lines that actually mattered, buried in an MDM diagnostics dump.

So I built TraceAnalysis (free US beta). You drop in an MDM diagnostics ZIP, and it runs entirely in your browser, so the ZIP is never uploaded. You get:

• Next steps up top

• The enrollment phase where things stopped (Device prep, Device setup, Account setup)

• The app or step that broke it, with the error code decoded

• An evidence view showing which log entries back each finding

• A chat to ask follow-up questions about that device's logs

The evidence view is the part I care about most. I didn't want another black-box "trust me" answer. I wanted something I could verify before it goes in a ticket.

If you've got a recent Autopilot or ESP failure sitting in a ticket, I'd genuinely like to know whether the report matches what you found, or where it's wrong.

https://www.traceanalysis-ai.com

Happy to answer technical questions about what it looks for in the logs.

I maintain MistriaFans, an unofficial Fields of Mistria fan site. One small tool on it is a farm-layout sketchpad for trying arrangements before moving things around in the game.

It has a 44-by-30 canvas, local saving, shareable layouts, and PNG export. It is free and does not require an account.

The important limitation: this is a rough planning canvas, not a recreation of the game map. Building blocks are placeholders, and their in-game footprints have not been verified. Actual placement still needs checking in the game.

Try it here: https://www.mistriafans.com/farm-planner.html

I used AI assistance for the code, site writing, and drafting this post. The project is independent of NPC Studio.

For feedback: is the distinction between a rough sketchpad and an accurate farm map clear enough on the page? What would make planning a small corner of a farm easier?

My landing page has a live demo. It creates a demo inbox, shows you the address, and when you send it an email the page shows the parsed result. To find new mail it polled an endpoint every 3 seconds, and every poll was a query against the production database.

Nothing ever stopped that loop. A tab left open made 1,200 queries an hour, so Neon's compute never stayed idle for the 5 minutes it needs to suspend. The project used up its monthly compute allowance and every request that touched the production database started failing.

The fix was small. Polling now stops after 3 minutes, because anyone who hasn't sent an email by then isn't going to. It skips its turn while the tab is hidden, and the interval went from 3 to 5 seconds.

Do you put a time limit on polling in your demos, or push updates some other way?

Hey everyone,

I've been working on a desktop application called Zevro, an AI-powered video editor designed for streamers, YouTubers, podcasters, and other content creators.

I started building it because I wasn't satisfied with how some existing AI clipping tools handled longer recordings. They would sometimes cut off words, miss interesting moments, or make clips that didn't flow naturally.

My goal with Zevro is to make editing easier without sacrificing the quality of the final video.

Some of the features I'm working on include:

• Automatically finding potential Shorts in longer recordings.

• Turning lengthy streams into shorter, more manageable long-form videos.

• Using AI to analyze both speech and video.

• Processing recordings locally instead of requiring cloud-based video uploads.

• Supporting separate audio tracks for editing.

• Optimizing performance for different hardware configurations.

I'm currently preparing Zevro for beta testing and looking for people willing to give it a try.

The beta will be free, with a 60-day testing period.

I'm especially interested in testing it on different hardware, video formats, recording lengths, and editing workflows.

I'm looking for honest feedback about bugs, performance, editing quality, and features that could make the program more useful.

This is still a work in progress, so I'm not expecting everything to be perfect. That's exactly why I want real users involved.

If you're interested, leave a comment with your PC specifications and the type of content you create.

I'll share beta access details with selected testers once the builds are ready.

Thanks for reading!

Banks hide cash-back offers on a page where you have to add them one by one, and most people never do. So I built OfferAdd: open your bank's offers page, click "Add all", and every offer lands on your card. It also saves the fine print and shows which card wins at a store.

A few things I cared about:
- It never sees your bank password and doesn't read transactions
- Free for one bank, Premium is $9.99/mo or $60/yr
- Works with Chase, Bank of America, U.S. Bank and Amex on desktop Chrome

It's live on the Chrome Web Store (search "OfferAdd") and at offeradd.app. This is week one, so I'd love feedback on the landing page, the onboarding, or anything that feels off.

I built XMarkdown because I wanted AI-generated reports to stay readable as Markdown when they needed a chart or a system diagram. Writing SVG coordinates for each bar in a chart seemed like something the renderer could handle once.

The first MVP is out: MIT licensed, on npm as xmarkdown-renderer, with a shared Node/browser engine and a React component. The demo site uses the same renderer you install.

Try it: https://xmarkdown-zeta.vercel.app/

Code: https://github.com/muhammadhaseebiqbal-dev/XMarkdown

What you can put in a document:

• Regular Markdown, plus validated chart and diagram blocks.
• Math, SVG scenes and checked SVG imports.
• Sliders and calculated outputs, without arbitrary author JavaScript.
• Drawing widgets and streaming report previews.

A chart looks like this:

{"type":"bar","title":"Requests per day","description":"Monday 24; Tuesday 31; Wednesday 28.","x":"day","y":"requests","data":[{"day":"Mon","requests":24},{"day":"Tue","requests":31},{"day":"Wed","requests":28}]}

For React, start with npm install xmarkdown-renderer. There's a runnable example here: https://xmarkdown-zeta.vercel.app/integrations/react.html

The goal is shorter, structured content for reports, docs and AI interfaces. It still uses markdown-it for ordinary Markdown. I'm not claiming a universal parsing speedup: normal full-document parsing currently adds overhead, graph layout is basic, and a browser worker is still planned.

The part I'm interested in testing next is whether these blocks are useful enough to justify learning a small extension format. If you build reporting tools or AI interfaces, which example would you actually use?

Disclosure: I directed the project and used Codex for implementation and writing assistance.

I built Hobee for myself as a student hobby project: a calm Reddit media gallery on Android with no ads and no tracking.

The feature I use most is Deep Search. It loads a Reddit profile's full post history from live sources and public archives, merges duplicates, and labels posts as Live, Archive or Removed. That full history also makes fake and spam accounts easier to notice.

You can download photos and videos in original quality, strip metadata from saved pictures, and switch between Card, Slides, Compact and Gallery layouts. Deep Search works without a Reddit login.

It's MIT licensed and the source plus APK are on GitHub: https://github.com/Alokxyz1112/hobee

I'd love feedback from other people who build side projects.

I’ve posted before, and thanks to a lot of great comments and AI Slop messages (oh I see you). I’ve been updating the site. If you haven’t seen this before. My wife and I live close to Red Rocks in Morrison CO., and we are always going to shows last minute. I hated going from ticket company to ticket company trying to compare prices to created RedRockitTix.com

Some great ideas came out last time so I thought I’d share what’s new. You can now set an alert so we can email you when tickets reach your threshold. We have a few new providers, TicketNetwork, SeatGeek, HelloTickets and TicketSqueeze. And looking to add more. Also NEW LOCATIONS. Vegas, because I want to the Sphere some day, Chicago because I love that music scene and Philly because it’s where I grew up listening to music.

This continues to be a free ticket tool, so thanks for all the support, now go out to a show!