I'm all for creating new frameworks that are faster and more secure. But I don't see how this one relates to Wordpress (not in PHP, serverless, not "plug and play", dependent on Astro, "AI Native"…).
It looks like a good open source project, but just call it a new CMS. I think calling it a "spiritual successor to WordPress" is just to gain some marketing points.
These road signs are iconic. They’re noticeable but not distracting. They inform without imposing themselves. There’s something very soothing about them.
If you’ve ever taken the A10 motorway France between Bordeaux and Paris, it’s about a 500 km stretch that is fairly straight and, thus, a bit boring. But seeing these golden signs along the road was always a small event for me as a kid. They act as sporadic milestones: every time you see one, you know you’ve made progress and entered a new region.
Those monuments (from humans or from nature) should be obvious knowledge, but I generally don’t know any of them. It helps pacing the road trip, and be able to say “Mom, I’m at the level of the [Sainte Baume, for me]”.
They are shown on Michelin maps and atlas. We love to travel using the atlas and stopping on interesting sights or roads. Usually in France you can go from A to B the fast and boring way, or the slow and scenic way which is perfect for holiday time
Interesting. I used Expo recently and loved the development experience. I also built a simple iPhone app with Swift, and it was a decent experience. I have plans of building another iPhone app and was considering Swift again, which would make me miss building an Android app, but maybe Skip would allow me to do it anyways.
Biggest downside to SwiftUI development is lack of hot reloading. You can use the Inject framework but it’s fragile. This also makes it harder to iterate on with agents.
Small views don't solve this for human use either. The only solutions for fast builds are to stop using SPM and also to adopt the "microfeatures" pattern with interface stubs and dependency injection so that very little must be rebuilt/linked. This is a huge change for many projects and carries ongoing development maintenance overhead so it is not a trivial decision to make.
Yes I think on mobile, having only the list scroll would be great. I actually had the Apple alarm interface in mind for a bit but thought implementing it would be more difficult. But you're right, it's probably a better experience.
For number 2, that should be possible, since I have the position of each item in the list (and the position of the list itself. Using a <canvas> might be the way to go.
For number 4, my main concern would be that it would feel like "scroll-hijacking". What I did however is prevent the picked item from going beyond the list, in both directions.
Number 5 is a good idea as well, easy to implement.
Another suggestion is showing an empty slot (selected item with less opacity and dotted border?) and displacing/scaling the picked item to show that it's been picked up. I would immediately connect it to picking up a book, CD, etc. from a shelf.
I think you should add some kind of marker to show where the item was picked up from and thus what would happen if the operation was cancelled, and an empty slot is perfect for that.
It looks like a good open source project, but just call it a new CMS. I think calling it a "spiritual successor to WordPress" is just to gain some marketing points.
reply