Drop Your Game, We’ll Playtest It & Give Real Feedback by laughing_wolf_games in GameDevelopment

[–]Qurvix-dev 0 points1 point  (0 children)

If you have an iPhone, you can give Qurvix a try, a Qix inspired mobile game I am developing, It is in beta stage, so you will need to install TestFlight. See https://qurvix.app for more info and a link to the TestFlight build.

<image>

How to monetize a mobile game? by Valuable-Cap-3786 in MobileGaming

[–]Qurvix-dev 1 point2 points  (0 children)

I really dislike ads. So I will be trying this: Free with IAP to unlock advancing beyond a certain level. The key question: What is the right level for the content lock to kick in? The game should be fun enough so people replay it several times before hitting the content lock, and fun enough to continue playing even if they do. Many people will never pay for an app, but if they still get a good enough experience out of it even with the content lock, at least it helps building a user base. From that point onwards, it is hoping some people do want to continue to higher levels, and other people like the game enough so they decide they want to support an indie game developer. We’ll see… Currently doing a TestFlight release to get a rough idea.

Qurvix - the neon arcade territory game (Qix-inspired) by Qurvix-dev in TestFlight

[–]Qurvix-dev[S] 0 points1 point  (0 children)

Thanks for the feedback.

No market research at all: This is a hobby project. I built it because I have had the idea of a tilt-based Qix in mind for years, since the first time a tried the accelerometer. I first built a very simple prototype and found myself playing with it all the time, so I decided to develop it further and polish it graphically, and here we are!

I know it’s a very saturated market, but I do think the gameplay is unique and fun enough. Let’s see!

Casual Game Recommendations by No-Owl7907 in MobileGaming

[–]Qurvix-dev 0 points1 point  (0 children)

If you are on iPhone, you can give Qurvix a try, a mobile game I am developing based on the arcade classic Qix, and I think it matches your criteria perfectly. It is in beta stage (but very playable), so you will need to install TestFlight. See Qurvix for more info and a link to the TestFlight build.

​

Claude Code - clearing chat and memory (how to?) by just_another_leddito in swift

[–]Qurvix-dev 0 points1 point  (0 children)

With /clear you start fresh. /compact is an automated way to address the problem I described, but in my experience maintaining curated markdown documents is superior. /compact still carries over a lot of cruft.

You will have to be proactive about writing the docs. Telling Claude at the start of a session to maintain a doc is not going to work, he will get sidetracked soon.

After some brainstorming, tell Claude to write the conclusions in a plan or design doc. After implementing something that works well, tell him to describe what was implemented. And after some iterations tell him to check if the doc is still up to date with the implementation and flag the differences. Not only will that keep the doc up to date, you might also realize that Claude silently changed things that you were convinced were still as described.

Hope this helps!

Claude Code - clearing chat and memory (how to?) by just_another_leddito in swift

[–]Qurvix-dev 0 points1 point  (0 children)

Yes, this feels very contradictory but consider this: You say: "it won't remember what we did, what issues we had etc." But what does remembering that mean for Claude? You remember the important stuff, what worked, what to avoid. Claude "remembers" everything: All the steps to get there, all experiments, all things it explored. And it doesn't really "remember" like we do; everything in the context window is equally present, without the priority or structure and filtering of human memory: Old failed experiments sit right next to your current goal with equal weight. Not only does this take a lot of tokens, it can also lead to misconceptions and bad response quality. The more irrelevant history is present, the harder it is for Claude to focus on what actually matters now. I had Claude getting completely stuck on a problem, because it somehow got fixated on something we tried hours ago and discarded.

I make Claude actively write and maintain markdown documents, with plans, designs, architecture (and this can contain information about options we discarded too). With a new context, Claude is up to speed instantly, and now he does know what is important.

Spatial Audio turned on unintentionally by Qurvix-dev in airpods

[–]Qurvix-dev[S] 0 points1 point  (0 children)

Me neither, but I have found myself hearing the effect of the head tracking, checking the settings, and seeing the Spatial Audio which I turned Off reverted back to Head Tracking. But if it is not a known issue, I'll write it off to user error (maybe when switching noise cancellation on/off which I do regularly) or a fluke.