My UX feedback is that I had a natural inclination to click on one of the response comments to my query and expected to be redirected to that hn post and if possible scrolled to the comment. I know why you might not want that but as long as you’re using query Params and not doing anything weird with browser history I’d almost certainly toggle back.
I could definitely use this as an alternative to hn algolia for some things but it’s going to be hard for me to remember. I’d recommend doing this as a browser extension or something so it’s not 100% lost in the void.
Thanks for the feedback! That feature is there, just not discoverable enough!
Try clicking on the relative time (e.g. "over 1 year ago"). Should take you immediately to that comment on HN, and you can then hit back in your browser to return to Hacker Search.
Yeah, I had a similar thought. If they just removed the ai or only focused on building a voice command to mobile app sdk there could be something viable there. Sadly that’s just not what they made at all.
Thanks! Tauri seems great, and there are a couple other options I was discussing with someone else recently too [1]. Trying to get handle on what's mature enough these days for a multi-platform app.
Thanks! I'm hoping to use Tauri or Dioxus if possible, just not sure if mature enough. Gotta figure out the data model first, which is independent of that choice, so not in a big rush to choose right now.
I love ink & switch! I think Martin, Geoffrey, and the whole team are crazy smart.
There's a whole bunch of approaches to universal versioning and I think floro is one of a few upcoming techniques in the ether.
From my limited understanding of their approach, it looks like they're going to be really focused on things like rich text diffing, which is not something I think floro is particularly well suited for. I think floro is really great for things that end up getting consumed as code rather than something like note-taking. e.g. static assets & i18n.
It's really exciting to see this space actually beginning to blossom though!
I put so much effort into that and you are probably the only person on earth who has actually read that thing in its entirety (aside from my poor, ex-midwife, mother who has no idea what I'm talking about).
> but am wondering if you're planning to apply the same techniques to traditional designer working files.
I would love to. When I discovered the JSON trick I felt really confident that this was the inevitable direction of the project but after writing a few plugins I'm not exactly sure how practical I really think that is now. It's great for primitives but I'm apprehensive about anything that starts to get into the no-code territory. I think it's possible but there's some mathematical and UI challenges I've got to overcome.
To make something more complex than a TMS system I really need to make the schema language a bit more robust in a way that is probably beyond my engineering skills. I need to find someone who actually knows how to write compilers and understands category theory (not me haha). I think this could be applied to something more general like figma/sketch though and I hope it's a first step for someone smarter than me to fill that gap.
I'd be happy to hear about your project and share my learnings if you want to schedule a time to talk. I've put a tiny bit of thought into this problem and would love to pass on what I've learned.
The way I originally conceptualized floro was a way to version anything without requiring plain-text (ie. higher order versioning). I've strayed quite a bit from that belief and I think there's a lot of complex trade-offs involved in version control and what makes sense for specific use-cases. Floro would be trash for game development but that is an industry that sorely faces tough versioning problems involving graphical data.
Please feel free to reach out to me if you do want to chat. The discord for floro is listed on the website but you can also just check my HN bio for my email.
Oof, sounds ominous. I have not heard of them, so it's hard for me to know where they stumbled or draw comparisons to what we've made.
To their point though, I largely agree with this, "The only thing I’ve found to be effective at dealing with competitors in early stage companies is to ignore them."
Did you ever get a chance to use their product?
This is something that really motivates me about offline first/OSS stuff though. It will be inconvenient for those who adopt if we have to shutdown but it's still possible to use floro without needing our servers. You will end up having to host your own though.
I wasn't a professional designer so never had a need for layervault, but it had quite a bit of polish for its time.
Another app in the space has been https://kaleidoscope.app/ (Mac only) which is still around but doesn't market specifically to just images, I think the parent company has changed hands (was owned by Black Pixel, then Letter Opener GmbH, now owned by Leitmotif)
By page do you mean like your live website with the changes?
I've thought about this too and I think down the line the plan is to be able to attach screenshots to merge requests. However, as a reviewer you can also pull down the changes and test them against your production site locally. So you can alter between the main branch and the feature branch and compare the differences like that. The benefit of this over a screenshot is it lets you actually get to see something like the hover effect in action.
In the demo they clearly have a wysiwyg app allowing them to drag in the icon, so the project is already set up for "live demo". If i'm a non-technical reviewer, like a designer (their target market I believe), I shouldn't be expected to pull down changes and test locally (unless that part can be automated and made super easy to do without fuss).
Figma kind of already does this (visual diff) with some of their tools for designers, although i'm not sure how well that can be integrated into a full fledged web-app who's changes and reviews could be shared by designers and engineers.
> I shouldn't be expected to pull down changes and test locally (unless that part can be automated and made super easy to do without fuss).
It's super easy and there's no fuss. You literally just switch branches. It's really easy to think the experience is analogous to code but it's not really. There's not a complex IDE setup or any complex local environment setup -- so it really is like just pull the branch open your browser, navigate to your website and test the changes.
I could definitely use this as an alternative to hn algolia for some things but it’s going to be hard for me to remember. I’d recommend doing this as a browser extension or something so it’s not 100% lost in the void.