However, before that, i set up a blank project in xcode, used the xcode github integration to create a new repo on github, set up one xcode cloud workflow and use it to push one build to testflight. That way, you get all the automatic config of app ids, profiles etc, and xcode cloud can not be enabled other way. Then tell claude to migrate to xcodegen and to run it in CI automatically.

I've started to develop iOS apps from scratch using only claude code web (no mac), by setting up a "Branch Build" workflow in xcode cloud, and a skill that teaches claude how to check builds and fetch logs.

Along with a workflow that pushes any merge on main to internal TestFlight, the dream of developing iPhone apps on the iPhone finally lives. I've tried most options for this over the years and they never stuck.

These are simple apps that build in 1-5 min on xcode cloud. For larger builds it probably won't work so well.

I'm quite confused on _why_ they want next to act like this? You can use anchor tags to force a browser navigation, but what does it get you? You're still loading JS bundles and it's not like breaks anything like history or open in new tab. People put turbolinks in their rails app to get something that works half as well.

You could also use unstable_disableRuntimeJs on some pages and your will still fully degrade to act like a completely server rendered page.

For reverse proxy you can go the old and trusted route with e.g. Nginx, go fully managed with something like external rewrites on Vercel, or even hack together your own thing with edge workers.

For all from one system, whatever you're using for your backend, be it React (with Next.js) or Ruby on Rails, can probably also serve any kind of static content, but it might not be worth intermingling that based on your situation.

An ICE is no different than a bus in this regard. A flight is a totally different story, probably planned weeks in advance and stress starts on the morning the day of.

I'm freshly frustrated because I'm dealing with a random metadata rejection (on an "internal testing" build! nothing has changed!) just now.

Play Store rejections are either an algorithmic mystery or reviewer incompetence. I don't mean reviewer incompetence in using the (maybe unintuitive) app. I mean their internal review UI had some kind of unrelated error and they sent me a screenshot of that. Their own console UI even sort of urges you to just resubmit with a potentially meaningless change instead of opening an appeal / request. Feels like it's the worst of both automatic and human review.

The inline programmability of DataView and the Grid views etc are pretty killer. Unfortunately Obsidian is not for me, so I hope Logseq catches up.

I don't think it's all that useful, outside of some basic "making a shopping/packing/project list" type calculations. It's worth checking out if you're interested in the history though.

Unfortunately, I've been drawn in by the linking functionality in Roam/Logseq and cannot go back to a simple outliner, though this makes me want to.

I don't think I'm a fan of the animated cursor while typing. It somehow makes the typing feel slower, like it takes some physical effort for the cursor to push forward.

How you make the database connection work with serverless connection requirements seems like a minor issue. I haven't used it but it seems like next + prisma (+ tailwind lol) is the default stack of tutorial writers these days.

If I want to use some function, I often just import it and call it directly, instead of calling one serverless function from another over http. That means the function gets bundled into a few lambdas, but so far, I've had no issues with that. The monolith abstraction hasn't really leaked for me.

> it won't work well on ephemeral, serverless platforms or when using rolling deployments

That's... a lot of new applications these days.

Also worth a mention are the free tiers of the "cloud scale" SQL new kids Planetscale (MySQL/vitess) and CockroachDB (mostly postgres-compatible).

Then there is supabase which also includes a postgres DB and AWS where you can run a small RDS instance free for 12 months.