My 76 old Dad loves checking the TOTP on his phone and asking me to verbally read it out when I need him to accept a 2FA push notification to let me log into his bank or government accounts so I can do something for him.
He says it “feels like 007 stuff.” “AI will never trick me!”
We also have a duress code word, listed in the notes of that KeePass(ium) entry with the TOTP.
For us, Claude Design wrote one html file and a bunch of jsx files. What it built was quite functional. We used the “export” button to download the project as a zip file and I placed the contents into a directory in my monorepo. Then I wrote an about 5 paragraph prompt for Claude Code, sent it with bypass permissions (CC is running as a different, non-root user with no LAN network access), and went to bed. The next day, viola, it turned prototype jsx into tsx (+ server-side ts) that mostly conformed with my existing stack.
I’ve been trying to find a good way to let my Dad keep tweaking the new version but haven’t so far. For now he continues to work (using CD) on the jsx prototype. I can do another export later and CC could use git diff to see what changed and realise those same changes in the “real” version. But there has to be a better way.
This isn’t going to replace Figma. It’s going to replace the people who use Figma.
My 76yo Dad just used Claude Design to make a simple commercial tenancy/lease management CRUD app. We handed what he built to Claude Code to implement within my existing business tech stack. It perfectly followed my coding & testing playbooks (basically a multi-file CLAUDE.md with prompt & command hooks to evaluate conformance). It works… exactly as my Dad imagined.
Now, mind you, my Dad had some outdated UI expectations (he asked Claude Design to style use a Windows 98 aesthetic!), but my point is: we just built a fully-functional, deeply tested, domain-expert-designed app, in less than a day.
I tried this on a local project. It looks very jank and the math falls apart quickly. Unfortunately, using a fixed axis-aligned grid for rotating reference frames is not practical.
One to thing I wanted to try but didn’t, was to use dynamic axes. So once an entity is created (that is, a group of voxels not attached to the world grid), it gets its own grid that can rotate relative to the world grid. The challenge would be collision detection between two unaligned grids of voxels. Converting the group to a mesh, like Teardown does, would probably be the easiest and most effective way, unless you want to invent some new game-physics math!
I think the word “solve” is better than “hide” here.
Fusion 360’s heuristics are so good that I rarely run into these problems. When I do, it’s usually because it was a drastic change to a previous feature in the timeline and I’m expecting to encounter issues because it’s a really fundamental change.
I wonder, is Microsoft doing “outsider trading”, where they covertly pipe analytical data to the executives’ independently-owned stock trading houses as “tips”? They’ve had access to so many corporate internal emails for so long, with MS365, but Copilot is the perfect way to mask such analysis. Also Copilot would be good at analysing emails and providing useful “tips”.
The Steam Link, also from 2015, is also still receiving updates! My partner and I use ours regularly to play co-op games on our TV. I really appreciate the efforts of whomever is keeping it running.
Too much speculation. Take the 18th amendment one. Maybe prohibition did have the desired effects, in addition to the undesirable side effects. The two are not mutually exclusive.
I know little about stocks, but I've heard China doesn't allow shorting stocks and many other "advanced" stock products/instruments. You can buy, sell and trade stocks, and nothing else. They also audit to ensure stocks are not oversold/traded (e.g.: selling stock you don’t own in the hopes you’ll obtain some in time to fulfil an order).
As you’re a solo dev, one of your most important resources is your mental capacity. Native platforms & their dev stacks are a world of their own.
Going with WebView allows you to spend your time on other things that matter more. It also helps you prototype quickly and get a feel for what works.
Later, after you have a better, more solid idea of what your game is, if performance is an issue, then you can convert parts of it (or all of it) to native.
(By the time your game is done, I suspect the mobile app dev landscape is going to be quite different than what it is now.)
Try Zed. Open-source (GPL+Apache), reliable, fast, not bloated at all, decently configurable, amazing remote-host support, Vim mode, AI stuff totally optional, extensions/lang-servers available for many languages, and... well overall I find it very neat and polished!
(I'm not associated with Zed, just a happy user looking to share the goodness.)
Or maybe Roblox is causing harm to children and nationalist governments are the fastest to both recognise and respond to the issue.
We can speculate all day, but we should try to analyse these sorts of things from a learning perspective. What can we learn from Russia, China, etc? How are they better?
Native escape hatch, for when you need native capability. For example, my app uses the Zebra DataWedge API on Zebra Android devices.
Native experience for users, where the app appears in their app drawer/library. The app doesn’t disappear randomly like shortcuts do on iOS (maybe this is fixed now?).
Better DX for certain features, like notifications, storage, control of caching, local network device access, etc.
I just rolled my own. I always find frameworks bring too many “weird errors” that waste my time trying to figure them out. Also, they’re just another thing that needs upgrading eventually, and they love to COMPLETELY change their APIs between each major version. (“FrungisFactory is deprecated! Try the new async-fibre-layout BloopisGrid now before we completely delete that thing that worked perfectly for you!”)
The platforms provide more than enough capability to build basic WebView apps with minimal effort, and usually the DX is good.
You can still have native views that appear over the WebView for certain tasks. I think you can also provide your own rendering context for <canvas> elements, so you could roll your own <video> element for showing the current camera view. Either way, you can still have full native camera control without having a 100% native app.
He says it “feels like 007 stuff.” “AI will never trick me!”
We also have a duress code word, listed in the notes of that KeePass(ium) entry with the TOTP.