A project by Joey Gilles
I’m Joey Gilles. Everything Joey is my independent project to make technology more useful in my day-to-day life. Core is the app at the center: one place for AI, tools, and the projects I’m working on.
Why I’m doing it
I have more ideas and interests than I can keep up with by hand. I want technology to take care of the repetitive parts—following updates, organizing projects, building and testing apps—so I can spend less time managing the process.
Core is the app. Everything Joey is the bigger collection of projects around it. It’s early, and I’m building it one useful piece at a time.
What I’m building and exploring
This covers the app, the systems that support it, and the experiments I want to turn into useful projects.
I’m building one iPhone and iPad app for chats, project context, tools, and memory. My longer-term goal is to run capable AI locally on the iPad while keeping the iPhone useful as a full client.
I’m building a control system for running long tasks, connecting AI agents and tools, checking what is healthy, and resuming interrupted work. The goal is less manual project management and safer recovery.
I’m organizing research and briefings around the things I follow: TV and movies, Baby Three and Miniverse collectibles, Chicago Fire, new technology, and local news. I care about reliable sources and catching meaningful updates without a flood of repeats.
My long-term goal is to build reliable income that takes very little ongoing work. I’m comparing software, referrals, and other legitimate options by setup, recurring effort, payout, risk, and realistic potential. Nothing is presented as income until it’s actually earning.
I’m exploring local AI, ways to run games I own on iPad, and what new hardware can do. I’m also interested in legitimate beta programs, hands-on product trials, and giving useful feedback on devices and apps.
I’m connecting source control and build services so app projects can be built and checked more reliably. I also want to share clear examples of what works, what I learned, and what still needs work.
Tools you can use
Small, practical releases for people running local automation on macOS.
Read-only diagnostics for common launchd, executable-path, plist, and resource-pressure problems on macOS.
Secure checkout via PayPal. Apple Pay and credit/debit cards appear on supported devices. Venmo is not accepted.
Reusable templates and tested patterns for safer, recoverable local automation and local-AI workflows.
Secure checkout via PayPal. Apple Pay and credit/debit cards appear on supported devices. Venmo is not accepted.
Paid releases are frozen QA archives. Mac Automation Doctor SHA-256: 0b70174d5d04c943c47e065b329ed0b0aaafe8cbae3975a904878d4be343851f
Local-First Automation Control Kit SHA-256: 76fd0265aef0cdd3d7279ec74840669d92c79d8fac986571e607f3134fdc3683
Where things stand
Last updated
| Area | Stage | Current focus | Next step |
|---|---|---|---|
| Core app | Planning | How iPhone and iPad share information | Build a usable first version |
| Automation | Getting it set up | Tasks that keep running and recover cleanly | Make it easier to spot and fix a stopped task |
| Updates and research | Improving coverage | Sources, completeness, and duplicate stories | Tighten briefings and alert rules |
| Income ideas | Researching | Setup, effort, and payout rules | Focus on legitimate options with little upkeep |
| App builds and devices | Active experiments | Build services and device compatibility | Get more prototypes to a usable state |
The bigger goal
I want a setup that can take a project from an idea to useful, verified progress—with local devices, online services, and background automation working together. I want clear costs, honest status, and my approval for decisions that affect my accounts, money, or private information.
A few ground rules
These matter as much as getting something to work.
I’m interested in results I can show and use, not big claims about what might be possible.
Research should be traceable, and uncertainty should be called out.
I stay in control of account access, payments, and sensitive personal decisions.
Start with the devices and free resources I have; make costs clear before anything changes.
Partnerships and access
I’m interested in legitimate product-testing and beta programs, device loans or review access, developer tools and compute credits, and small collaborations that can lead to a working prototype. I can offer hands-on testing, thoughtful feedback, and a clear account of what I learn.