Six weeks and I still can't sign a binary.

I have an app that's finished. I can't ship it. Not because of a bug, not because of a rejection, not because I ran out of runway. Because a form is in a queue somewhere at Apple, and it has been there since July 2.

Here's the short version. I formed an LLC — Second Chapter Technologies — and did what you're supposed to do: I started converting my Apple Developer account from Individual to Organization so the apps would be published under the company instead of my personal name. Reasonable. Boring. The kind of administrative housekeeping that's supposed to be invisible.

Instead, my account went into a pending state and my ability to sign a binary went with it. Six weeks ago.

What "pending" actually costs

I want to be precise about this, because I think the word "pending" makes it sound smaller than it is.

While my account sits in conversion, I can't sign builds. Not for the App Store, not for TestFlight. The app I've been building doesn't go to testers. It doesn't go to review. It doesn't go to the three people I most want to hand it to. It just sits on my machine, finished, doing nothing.

I've contacted Apple about it five or six times now. Every response has been some version of we're experiencing higher than normal volume. No error to fix. No missing document to send. No estimate. Just backed up.

I'll be fair here: I don't think anyone at Apple is doing this on purpose, and the people answering my emails aren't the problem. Support agents can't manufacture a decision from a team they don't sit on. That's a resourcing choice made well above them.

The part that actually keeps me up

Everything above is annoying. This next part is why I'm writing it down.

The app is called Remember Project. It records your family's stories in their own voice — you ask a question, they answer, and the answer is kept. That's the whole thing.

I built it because I can't remember what my grandparents sounded like. I remember the house on Hortencia Street in Brownsville. I remember waking up to the sound of them in the kitchen. I could not tell you, today, what either of their voices actually sounded like. There's no recording. There was never going to be a recording, because nobody thinks to make one until the window has already closed.

My parents are 82 and 76.

That's the clock I'm actually running against. Not a launch date, not a quarter, not a competitive window. A real one, and one I don't get to negotiate with. Every week the account sits in that queue is a week I'm not putting the finished thing in front of my dad and asking him about his father.

I know how that sounds. It's a first-world problem wearing a heavy coat — nobody at Apple knows my parents' ages, and it isn't their job to. But it's the honest answer to "why are you so worked up about a support ticket." Because the support ticket is standing between a finished app and the two people it was built for, and I have no idea how long the ticket will stand there.

Today I got frustrated enough to send Apple a genuinely strange request: can I cancel the conversion, revert to my individual account, ship, and convert later?

I don't have an answer yet. But I want to be clear about what that email represents. I would rather undo six weeks of process and publish under my own legal name than keep waiting for permission to sign my own code. That's not a strategy. That's what running out of patience looks like when you write it professionally.

What I'd tell you to do instead

If you're an indie developer thinking about incorporating, here's what I've got.

• Ship first. Convert later.

  This is the one that matters. Publishing under your individual account and moving to an organization afterward has real friction — the transfer isn't free of paperwork either — but it's friction you experience while your app is live and in front of users. Converting first means the friction happens while you're frozen. Same paperwork, radically different cost. I did it in the wrong order and I'm paying for it in the only currency that isn't recoverable.

• If you must convert, do it during a dead period.

  Not while a build is close. Not while you're in review cycles. Not while you have anything you might plausibly want to ship in the next two months. Treat the conversion as a hard freeze on your ability to ship, of unknown duration, and schedule it like one.

• Assume no timeline and plan accordingly.

  I went in assuming this was a two-week formality. Nothing Apple published told me otherwise, and nothing they've said since has corrected it. Build your plan around "indefinite" and you'll never be wrong.

• Keep asking anyway.

  I don't think my five or six emails moved anything. I also don't think silence would have. It costs you very little to stay in the queue politely and visibly.

• Separate what's blocked from what isn't.

  Six weeks of not being able to sign a binary is six weeks I could have spent doing nothing, or six weeks of accessibility work, legal review, and writing. I did some of both. The days I chose the second felt considerably better.

Where this stands

As of this afternoon: accepted. Six weeks to the day, near enough, and it landed within hours of me asking to undo the whole thing. I don't think those two events are related. I have no way of knowing, which is sort of the point — I never got a reason for the delay and I didn't get one for the resolution either.

What I'd want you to take from this isn't "it works out eventually." It's that I had no information the entire time, and no way to plan around a process with no published timeline and no status beyond pending. Six weeks was the number this time. It could as easily have been two, or twelve. Nothing I did moved it.

So the advice stands, and if anything the ending sharpens it. If you're weighing convert-now against ship-now: ship now. The paperwork will still be there afterward, and you'll be doing it with a live app instead of a frozen one.