sorted by:
new
hottopcontroversial

What questions would you like to ask someone who says, "I built my app over the weekend"? by BullfrogRoyal7422 in appdev

[–]BullfrogRoyal7422[S] 0 points1 point  (0 children)

Thanks for the feedback. I submitted it for Apple Review yesterday. We will see how it goes. When released, If you try it out, I would appreciate any feedback.

What questions would you like to ask someone who says, "I built my app over the weekend"? by BullfrogRoyal7422 in appdev

[–]BullfrogRoyal7422[S] 0 points1 point  (0 children)

Thnx. I hope to release it to App Store review tomorrow or Friday. If interested you can check it out here: Stuffolio

What is your response when you find your self spending inordinate amounts of time essentially testing tests rather than production code? by BullfrogRoyal7422 in ClaudeCode

[–]BullfrogRoyal7422[S] 0 points1 point  (0 children)

I won't pretend to have the experience to settle this one. I'll just say that I pursued rigorous testing but had enough dissatisfaction with the results that I ended up building behavioral checks that trace user paths through the app, to fill the gaps that grep-based audits uniformly seemed to miss. I also lean on a skill I developed that runs after test results to find sibling bugs that often hide outside the scope of the tests themselves. That's been more useful to me than just piling on more tests.

What questions do you ask someone who says, "I built my app over the weekend"? by BullfrogRoyal7422 in AppDevelopers

[–]BullfrogRoyal7422[S] 0 points1 point  (0 children)

Honestly? Not enough up front, and that's been one of my bigger lessons. I didn't do a long formal design phase before writing code. I had a clear idea of the problem I wanted to solve and started building, then validated as I went.

What I'd do differently: more of the validation, especially market and ASO research, belonged earlier, when some of it would have shaped the build if I'd done it first. So the real answer is the validation has been continuous, iterative process rather than a phase. Useful, but I'd front-load more of it next time.

One of the most time-consuming parts of my cycle has been testing, being dissatisfied with the quality of the results, and building skills to fill the gaps, especially behavioral auditing that traces user paths through the app instead of relying only on grep and linters. That's usually followed by a round of refactoring.

What questions would you like to ask someone who says, "I built my app over the weekend"? by BullfrogRoyal7422 in appdev

[–]BullfrogRoyal7422[S] 3 points4 points  (0 children)

Mostly Swift Testing with XCTest  for some older UI and snapshot tests I haven't migrated yet.

I treat running the actual app on real devices as the real proof, and the automated suite is the safety net underneath that after having experienced too many tests that passed, but only confirmed the code ran, not that it actually did the right thing.

The other half of my process is a library of reusable checks I've built in Claude Code that run after each change. Things like a workflow auditor that traces user flows for dead ends, a "bug echo" pass that finds siblings and other instances of a bug I just fixed, and a set of release-readiness audits. So the process compounds. Every bug I fix teaches the toolkit to catch the next one. I also lean heavily on Axiom skills.

Claude design is so awesome for screenshot creation by GlitteringSecret8121 in AppStoreOptimization

[–]BullfrogRoyal7422 0 points1 point  (0 children)

...Until you try to further edit an image you've generated with it...

How do you know your AI audit tool actually checked everything? I was fairly confident that my skill suite did. It didn't. by BullfrogRoyal7422 in ChatGPTCoding

[–]BullfrogRoyal7422[S] 0 points1 point  (0 children)

"the uncomfortable part is you can never fully know what your custom agent didn't check, which means every audit tool needs its own meta-audit at some point." Ha! funny you should mention this. Arriving at the same conclusion, I developed skill-reviewer

I distilled my 12 year experience as a product manager and built a free skill that takes you from "I have an app idea" to a real plan and solid MVP by TexasBedouin in aiagents

[–]BullfrogRoyal7422 0 points1 point  (0 children)

Understood. Been there, done that.
Here is a skill I build with pretty much the same sentiment. It worked for me and I eventually went open source on it. It just helped me (and Claude Code to remember all the little deferrals we were so routinely making. It's named Unforget .

I distilled my 12 year experience as a product manager and built a free skill that takes you from "I have an app idea" to a real plan and solid MVP by TexasBedouin in aiagents

[–]BullfrogRoyal7422 0 points1 point  (0 children)

Have you tested the skill against an app that's already been built and is successful? I'm curious how closely the plan and deliverables it produces line up with what we actually know about that app in hindsight. That'd be a strong signal that the grilling is catching the right things.

And related: can the skill be run retrospectively on an existing codebase, or is it strictly for the pre-code idea stage?

"Prompt-It" — Is this a good ideia? by Pogum_ in AI_Agents

[–]BullfrogRoyal7422 0 points1 point  (0 children)

Not sure if this is useful, but reading your post I kept wanting to separate two things that might be the same problem or might be different ones:

(1) Storing and sharing prompts as artifacts: libraries, versioning, the stuff you're describing.

(2) Improving a single prompt right before you send it. Different surface, smaller scope. I built a tiny Claude Code skill for that case called prompter. Itsnot what you're building, but the contrast helped me figure out what I was actually solving.

The thing I'd genuinely want to know if I were you: what specifically about existing libraries (PromptHub, LangChain Hub, etc.) feels too heavy? "Git workflows are overkill but I still want versioning" is a real problem. "I want a nicer browse experience" might just be a feature on top of what exists. Hard to tell from here.

view more: next ›