A project by Joey Gilles
I’m Joey Gilles. I’m building Core, automating the work around it, and testing what my devices can do. I’m also exploring authorized Apple device-security research and making small Mac tools people can use today.
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
From a personal AI workspace to security research and small products, these are the areas I’m actively building or exploring.
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 testing local AI and ways to run games I own on iPad, while looking for legitimate opportunities to try new devices and software. That includes beta programs, developer hardware, product trials, and sharing useful feedback.
I’m connecting source control and build services to make app testing and releases more reliable. I’m also documenting what works, what breaks, and what I learn along the way.
I want to understand Apple’s security boundaries, study deeper access on devices I own, and identify vulnerabilities that can be reported responsibly and fixed. This is an early research goal; I’m not claiming to have found an exploit or built a jailbreak.
I’ve started releasing small Mac automation products. Longer term, I want to see whether the best parts of Everything Joey can become a reliable system other people can install, adapt, and pay for.
Security research
Looking for knowledgeable people to help shape a responsible research plan.
One goal is to study iOS, iPadOS, and tvOS security on devices I own, including whether deeper system access could support research or new uses. I want to learn how to find and report real weaknesses so the people responsible can fix them.
This work is exploratory. I’m not claiming to have discovered an exploit or created a jailbreak.
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 |
| Apple security research | Exploratory goal | Authorized scope and expert review | Define a responsible research plan |
| Products | Early releases | Practical Mac automation tools | Improve from user feedback |
The bigger goal
My long-term aim is to turn this from a personal setup into useful products while continuing to explore local AI, app development, automation, and device security. I want honest claims, clear costs, 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 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’d especially like to connect with Apple security researchers who can help me set a responsible scope and learn the right way to identify and report vulnerabilities. In return, I can offer careful hands-on testing, useful feedback, and clear notes about what I learn.