All the while management is breathing down your neck and asking 'why isn't it ready yet'.
Once the thing is shipped, then all the important people come out of the woodwork, who were surely there all along, 'supporting' you from behind the scenes, there are photo ops and important people shaking hands. If they feel particularly charitable, then you might get a seat at the table. There's talk of spinning up a team around the product, and people fall over each other to get to lead it.
But the thing is, most likely they don't need your expertise any more, not really, once everything works, you don't really have a negotiating position as a dev. They get some cheap juniors to fix the bugs and add the missing feature niggles - hiring 3 juniors might not even be cheaper, the point is management does not have to depend on you, they can play their human resource games.
'But only I can fix that complex race condition, that popped up half a year after development' - well if it was good enough with the bug for people not to notice it for half a year, it's going to be good enough for another half, until the new devs can fix it.
This applies to ambitious feature requests as well - if the code's good enough that the contract was signed, the business requirement was met, they can just kick the can down the road until they can fix it.
Funny, this is the complete opposite of my experience. Greenfield projects I've been a part of have had a ton of highly visible progress with _frequent_ updates to stakeholders basically from day 1. Same goes for complex additional features.
1. Reading technical papers where I use the pen to make notes
2. Sketching household projects (a few of the apps are very nice for this).
Outside of that, I simply want a real, physical keyboard most of the time.
I got HumbleBundle with a bunch of Pathfinder 2e PDFs cheap but I'm still tempted to buy the physical copies.
Or if you aren't a music person, are you into making movies? Final Cut Pro does have a subscription, but it's only $5 / month and the subscription is easy to start and stop. If your needs are simple, the free iMovie is pretty good.
Or maybe video isn't your thing. Are you a writer or poet? There are a lot of great choices for writing apps and the battery life of the iPad means you can work away from your desk all day.
Or if you like writing software, Swift Playground is fun. I found this to be a great resource:
https://github.com/uraimo/Awesome-Swift-Playgrounds
If you are into photography, Affinity Photo is fun. It doesn't have the AI features that Photoshop has, but for amateurs, it can get you pretty far. Plug in an external drive to your iPad and you can use it with a huge photo library.
And those cheap/free things are only available after dropping $1000 on a new iPad
* You sell a B2C product to a potentially global audience, so edge semantics actually help with latency issues
* You're willing to pay Vercel a high premium for them to host
* You have no need for background task processing (Vercel directs you to marketplace/partner services), so your architecture never pushes you to host on another provider.
Otherwise, just tread the well-trod path and stick to either a react-vite SPA or something like Rails doing ordinary SSR.I used to think Javascript everywhere was an advantage, and this is exactly why I now think it's a bad idea.
My company uses Inertia.js + Vue and it a significantly better experience. I still get all the power of modern frontend rendering but the overall architecture is so much simpler. The routing is 100% serverside and there's no need for a general API. (Note: Inertia works with React and Svelte too)
We tried Nuxt at first, but it was a shit show. You end up having _two_ servers instead of one: the actual backend server, and the server for your frontend. There was so much more complexity because we needed to figure out a bunch of craziness about where the code was actually being run.
Now it's dead simple. If it's PHP it's on the server. It's JS it's in the browser. Never needing to question that has been a huge boon for us.
The evidence suggests this isn't AR prep at all. I watched Apple's 20-minute design presentation, and their design team makes the same point repeatedly: Liquid Glass has very narrow guidelines and specific constraints.
Here's the actual design problem Apple solved. In content apps, you have a fundamental trade-off: you have a few controls that need to be instantly accessible, but you don't want them visually distracting from the content. Users are there to consume videos, photos, articles - not to stare at your buttons. But the controls still have to be there when needed.
Before Liquid Glass, your least intrusive option was backdrop blur or translucent pastel dimming overlays. Apple asked: can we make controls even less distracting? Liquid Glass lets you thread this needle even better. It's a pretty neat trick for solving this specific constraint.
So you'll feel like you're seeing Liquid Glass "everywhere" not because Apple applied it broadly, but because of selection bias. The narrow use case Apple designed this for just happens to be where you spend 80% of your phone time: videos, photos, reading messages. You're information processing, not authoring.
Apple's actual guidelines are clear: only a few controls visible at once, infrequent access pattern, only on top of rich content. The criticism assumes they're redesigning everything when they explicitly documented the opposite. People are reacting to marketing tone instead of reading what Apple's design team actually built.
[1] https://peoplesgrocers.com/en/writing/liquid-glass-explained
I would rather borders and color contrast to create visual separation anyway. That approach takes up less space. White space takes makes your UI less dense, but blur is even worse.
Either way… how does that relate to my keyboard being transparent? I don’t need to see a completely illegible blur of the colors behind my keyboard.
I just turned on the “reduce transparency” setting and it’s much better.
Just found the setting…thank you! It was actually driving me crazy. There’s still a bunch of really weird, unnecessary UX changes but this helps a lot.
That was my only fear when I toyed with Inertia, Django, and Svelte for an afternoon. When I’d get an error it seemed obscure or not indicative of the underlying cause.
What’s everyone’s experience? Inertia seems like magic. And that’s what scares me a little.
It is just a simple bit of glue between your Vue app and your backend. The docs are good, and it overall just feels solid/stable. Super excited to see the new changes that are coming too!
But I can't say the same with translations/localisation.
Honestly, the upside of 1 language is not that high. Don't be afraid of PHP, it isn't the same language it was 15 years ago. I've been programming JS for 10 years but only been using PHP for a year, it's weird but it's got some nice parts too.