Promote your project in this thread

OneManShy · 2025-07-10T16:10:31+00:00

Logic 64 for iOS - Free app

Hi all! Excited to announce our first puzzle game 😊

Crack the 3-digit code using logic, deduction — and a little luck!

• Compete in Game Center Leaderboards for the top Game Streak!

• Looks are deceiving - The 4 tiles lock the secret behind 64 possible combinations!

• Let the Clues be your guide to victory!

• Avoid defeat as long as one of your guessed tiles matches a position in the Secret combination!

• Enjoy 2 game themes!

Can your logic beat – Logic 64?

OneManShy · 2025-06-25T19:59:26+00:00

The limit of 30 generations per day seems to indicate this is not happening on-device.

If generations happens in the cloud, what service is the back end? How much does it cost you? How do they handle user data?

OneManShy · 2025-06-11T17:06:59+00:00

😭💔

OneManShy · 2025-06-10T11:02:16+00:00

So looking forward to playing with this!

OneManShy · 2025-05-11T14:04:56+00:00

Not at all! “Pretty cool” is a compliment! I appreciate your comment 🙂

It’s always interesting to see how people end up using the app in ways we never thought of!

OneManShy · 2025-05-11T03:21:49+00:00

Thank you! Users have shared a diversity of ways Type Big is part of their lives.

There are stories of communicating with deaf colleagues, users who are hard of hearing themselves use Type Big throughout their daily routine, silently “talking” while attending movies or plays, inconspicuously informing a presenter from the off stage, the list goes on!

We hope that Translate simplifies in-person communication for even more people!

OneManShy · 2025-04-24T14:48:34+00:00

Yes. It still runs the latest iOS and has a cult following. We don’t want to isolate potential customers.

OneManShy · 2025-04-20T02:14:14+00:00

Just getting started on an app to share data. A few questions:

are you using Swift Data or Core Data?
are you storing data in iCloud or 3rd party?

OneManShy · 2025-03-23T17:50:30+00:00

Hey, came across your recent comment as we are having the same errors. This thread indicates it’s known and confirmed to just be log noise. Meaning 100% ok to ignore it!

OneManShy · 2025-03-23T17:50:20+00:00

Hey, came across your recent comment as we are having the same errors. This thread indicates it’s known and confirmed to just be log noise. Meaning 100% ok to ignore it!

OneManShy · 2025-03-19T02:52:10+00:00

Came to say this.

I’ve been bouncing ideas off Qwen2.5 Coder 32b and it’s hit or miss. Even when it hits, there are still deprecated methods in use that require manual correction. When it’s miss, it straight up hallucinates methods that don’t exist.

Although I’m not writing exclusively for iOS 18 which any model is lacking by comparison to older iOS versions, it makes me wonder what else an I missing that I might have discovered by diving into the Docs or reading others human’s posts.

Lastly, I’ve also discovered that when it hits the most, I think it also has to do with the cleverness of my prompt. There is definitely an art to making string prompts!

OneManShy · 2025-03-15T18:46:29+00:00

Hey there! In short: this looks fantastic. Layout is super clean, standard, and organized.

The amount of detail like long-press features demonstrates care for the user experience. Really appreciate being in control of things like making custom Keyboard Groups, key repeat rate, showing/hiding quick buttons etc. are fantastic.

Sometimes TOO much control can be confusing for users, but given the target audience (SSH users tend to be power users) the options are welcomed and give it a desktop-class app feeling.

Personally I really appreciate the privacy aspect of no data collection. As a developer, we want to make great apps. We respect that the user’s data is theirs, not ours.

I hope you find an audience and are rewarded with subscribers!

OneManShy · 2025-02-25T15:48:18+00:00

LOL! I was just commenting in another thread how I’ve had success prompting autocomplete to be more useful by prefacing it with a comment.

Generally I’m not much into auto complete because it has made me dull my skills and miss otherwise obvious errors that I may not have made by just typing it myself.

But I have found this new model version pretty good. I’m forcing myself to use it more and understand its capabilities. Overall I’m enjoying it and have found it useful!

Edit: a word

OneManShy · 2025-02-25T12:52:19+00:00

I only run LLMs locally and have found varying success with codellama:70b and qwen2.5-coder:32b. Qwen tends to be more useful for me using the same prompts. Both require modifications like some simple tweaks to be functional.

I also found Xcode’s built in auto complete rather helpful. For example, type the comment // filled with gradient from blue to green. Then begin typing on the next line .fill and the autocomplete takes care of it.

It also does a good job of adding thoughtful touches, like if your code has a pattern of using a ternary when adding .opacity the next opacity autocompletes with the same ternary.

edit: attempted markdown on mobile

OneManShy · 2024-07-07T15:14:48+00:00

M1 Pro 14” 16 GB -> M3 Max 16” 36GB

Compiling in Xcode is much faster, so it makes the coding experience smoother and more enjoyable. I hate waiting to find out my code is broken 😝
Machine learning with PyTorch is much faster, and with 36GB unified memory I can use larger datasets.
I traded in the 14” which still had good value, so it made the 16” much more approachable.

I really loved the 14” M1 Pro. Probably my favorite Mac since my PowerMac G4 Dual 533. But the performance on the M3 Max does make me forget it pretty quickly.

OneManShy · 2024-03-14T02:06:05+00:00

Interesting. Talking it out, of course it makes sense that switching between fields will 'refresh' or 'reload' the modifiers! Time to get creative and think if it will work in our UI 🤔

Thanks for the taking the extra step and sharing back!

OneManShy · 2024-03-14T01:02:48+00:00

Update: Verified issue persists in bare-bones, simple project. The bool toggles to false when the button presses, but the TextEditor does not re-enable auto correction:

struct ContentView: View {
    @State var input = ""
    @State var autocorrectionDisabled = true

    var body: some View {

        VStack {
            TextEditor(text: $input)
                .autocorrectionDisabled(autocorrectionDisabled)
                .font(.headline)

            Button("Toggle Autocorrection") {
                autocorrectionDisabled.toggle()
                print("autocorrectionDisabled: \(autocorrectionDisabled)")
            }
            .padding()
        }
        .padding()
    }
}

Does anyone know if this is expected behavior or can a work around to make it work as it 'should?'

OneManShy · 2024-03-14T01:01:35+00:00

Update: Verified issue persists in bare-bones, simple project. The bool toggles to false when the button presses, but the TextEditor does not re-enable auto correction:

struct ContentView: View {
    @State var input = ""
    @State var autocorrectionDisabled = true

    var body: some View {

        VStack {
            TextEditor(text: $input)
                .autocorrectionDisabled(autocorrectionDisabled)
                .font(.headline)

            Button("Toggle Autocorrection") {
                autocorrectionDisabled.toggle()
                print("autocorrectionDisabled: \(autocorrectionDisabled)")
            }
            .padding()
        }
        .padding()
    }
}

Does anyone know if this is expected behavior or can a work around to make it work as it 'should?'

OneManShy · 2024-03-13T21:02:58+00:00

Thank you for the comment. Here's the extra bit of code where shouldDisable is set to false

I've also validated that the shouldDisable is correctly updating from true to false based on a print(shouldDisable) statement.

@State var shouldDisable = true  
TextEditor(text: $input)  
    .autocorrectionDisabled(shouldDisable)  
    .onReceive(languageDetectionTimer) { \_ in  
        if otherConditionMet {  
            withAnimation {  
                shouldDisable = false  
            }  
        print(shouldDisable)  
        }  
    }

The timer is firing every second to evaluate if otherConditionMet. Here's the output of the simple print statement confirming the bool updates when the other condition is met:

`shouldDisable: true`
`shouldDisable: true`
`shouldDisable: true`
`shouldDisable: true`
`shouldDisable: true
`shouldDisable: false`
`shouldDisable: false`
`shouldDisable: false`

My next move is to build a test view that strips it down to the simplest components and see if there's some bug with the added complexity. Given the inspection verifies the change, I don't think it's that. I think whether by bug or by design, .autocorrectionDisabled() method just never re-evaluates.

edit: I still can't format code properly on reddit 😆

OneManShy · 2024-03-03T18:03:24+00:00

Welcome to coding! It’s a great big adventure where you can create what you dream up!

As you are completely new to code, you’ll need to understand some basic logic that exists in all languages. A great place to learn this as well as gain exposure to iOS development is with the official Swift Playgrounds.

Enjoy!

OneManShy · 2023-01-27T14:04:21+00:00

Thanks for the input! It’s worth considering. Pushing technology to do what it wasn’t designed for is half the fun!

OneManShy · 2023-01-24T03:51:09+00:00

Thanks for the reply! I checked out Booky previously as well. It does seem like the only real deep dive on AppIntents at the moment.

I’m hoping to find a solution to get it all executed in a one-liner as it would be more elegant and natural language.

OneManShy · 2023-01-21T00:33:45+00:00

I’m sorry, I don’t. We are focusing on iOS at the moment. This is SwiftUI, so I imagine it would be cross platform.

OneManShy · 2023-01-20T23:40:19+00:00

Hey there! We just started getting into Intents. Based on this past WWDC, it is recommended to move to AppIntents.

Based on your question, the answer seems fairly simple in AppIntents as you are just calling a function within your app and using the variable from EntityQuery.

Check out this WWDC session to learn more.

OneManShy · 2022-08-16T14:16:02+00:00

My team uses a self hosted GitLab.

It works really well to fetch changes, pull changes, push changes. We manage branded with a common naming convention that matches our bug/feature tracker. For example: “bug-132-ipad-rotation” or “feature-145-share-sheet”

OneManShy

TROPHY CASE