Questions about the App

[RemoPro]

I have some questions about the app:

• The Bundle Identifier seems simple to me, do you want to change it to something unique like com.trey.launchback ?
• In some files the word MARK is written, looks like you used AI to help you (I also used it)
• Do you plan on using Folders for the files in the Folder structure like Views, Models etc (I can do a Fork and then do those changes)
• The app is a solution for macOS 26+, so maybe consider increasing the Minimum Deployment Target of the app to 26.0
  • A new icon built with Icon Composer would look great, also since You took a different name than the Apple Original so a different icon would make sense right?

Sugessted Folder structure:

Happy to hear from you. Can you leave that Issue open for questions?

[trey-a-12]

1. Sure thing. "Program" in the bundle identifier was more or less a placeholder in earlier versions before I knew what I wanted to name the app. (Fun fact: This is even reflected in the video demo on the ReadMe where it was still called "LaunchpadGlass," reflecting how this was originally just going to be a 1:1 clone of the original Launchpad with Liquid Glass before I became more... ambitious.
2. Yes, this was AI-assisted. I am going into college with cybersecurity and a bit of computer science in mind, so I wanted to work on both my own programming capabilities as well as comfort with AI (if we're going into such an AI-assisted field, you might as well learn how to use it too, right?) and prompting. All ideas, troubleshooting, prompting, major "solutions," and other things have been entirely done by me, though.
3. Yes. Better organization is 1000% planned as I refine the folder structure and build out core features.
4. It IS a solution for macOS 26+, but I intentionally set it as old as possible for compatibility sake. Once LaunchBack does eventually get 100% of classic Launchpad functionality and begins to surpass it, it could hopefully be seen as a "Launchpad+" even for users of older macOS versions. Sure, as feature support is dropped or if major changes are made in newer macOS versions that would improve LaunchBack, I would gladly move the deployment number up, but at least for now, things work perfectly (even with Liquid Glass) on macOS 26 Tahoe Beta 5.
5. I actually DID build this icon with Icon Composer back in Tahoe and Icon Composer Beta 1, and it is currently just a slightly-tweaked Launchpad-style icon (almost 1:1), but I am planning on making a more "custom" icon in the future. For now though, I want to keep this icon, and perhaps I'll even add an icon switcher function like OpenShell's where you could use a "classic," "LaunchBack," and even "custom" icons!

[RemoPro]

No git configured yet?

Another thing that I noticed is that you didn't configured git in the Xcode-project?
You can log in with your GitHub-Account in Xcode and then add a remote repository. But I'm not entirely sure how well that now goes when the files are all here and git is not yet enabled. Then you also need a .gitignore file to ignore changes in the xcodeproj file.

[trey-a-12]

1. Apologies for the delayed response, just moved in to college 🥳
2. I actually tried configuring a Git repository when I first set up the project, but for whatever reason, it kept failing to initialize. This was on Tahoe Betas 1 and 2 with Xcode 16, where I also could not get the AI models working either. I want to revisit this soon, though, particularly since initializing a Git repository for a second app project of mine created after LaunchBack DID work after downloading the Xcode 26 Beta.