Great job with this! Just gave Waywise a download and love the user interface – especially the localised language prompts. The different UK dialects are spot on and very funny. I'm heading to Spain soon so will give this a whirl, with the restaurant recommendations / translations.
Out of interest, have you had any problems with the AI hallucinating when generating new city guides?
I definitely had some hallucinations to start off with. Mainly when I hadn't quite nailed down the prompts and it was just making up train stations in Oaxaca (turns out there aren't any intercity train stations in Oaxaca). From my testing though they all seem to have been ironed out but I'm constantly tweaking to improve.
We've been using Plausible for over four years at our startup. Always reliable, simple, and fast metrics. Open source is tricky to scale and maintain while also ensuring a consistent income. Happy to hear they're making this change to protect their brand, IP, and ensure a sustainable future for the team.
Back in 2018, I worked on projects where we used Ant Design. At the time it was one of the best choices out there for a quick project, as it had all the standard components with a relatively good design out of the box. Since all the easter egg fiasco / css bloat I've avoided using it.
These days, there's just much better options such as shadcn/ui [1], chakra [2] or radix [3] which when paired with frameworks such as floating ui [4] are just much better.
shadcn/ui is pretty terrible unless you already have a an entire design system you're planning on replacing the defaults with anyways.
Radix Themes (not Primitives) has the WorkOS look without awful color choices and the whole "pretending not to be a component library" gimmick https://www.radix-ui.com/
> the whole "pretending not to be a component library" gimmick
Literally the first line says that it's a component library :)
Snark aside, I'm gonna defend Radix Themes. I agree that the configurations they show on their website aren't great (and also that they should pay more attention to pixel alignment), but they have the most consistent structure I've seen, with well-defined tokens, great composability and flexibility for overrides.
I've found that, with the parameters they provide, I can get a design that is close to what I would've done myself anyways. Eventually, I guess I'll look into adding some light overrides to add a bit more shadow and fix some of the rougher edges.
Nice work collating all the tax data, how do you ensure that the tax data stays up to date? And is there any way you could add a filter for countries that are part of the VAT OSS scheme? As Europe doesn't necessarily mean part of VAT OSS.
Thanks! We keep track of changes on a monthly basis and update relevant information accordingly.
Just to clarify, do you want a filter specifically to toggle between countries that are a part of the VAT OSS scheme and countries NOT in VAT OSS scheme?
Oh nice, super helpful. For me being able to filter by countries that are part of the VAT OSS scheme, since many of us running SME’s submit the tax manually, and it’s helpful to have a SSOT for the VAT OSS rates.
Just took a look - this is a good csv no doubt, but looks like you're focused on countries with VAT and not those with GST, sales tax, and consumption tax right?
Yes you're right. It is not complete and had plan to fix all that a couple of years ago but put it on the back-burner. I'm still happy to merge PRs upstream from motivated contributors! :)
This is such a good idea that's simple and well executed. The number of times, I've had to sift through YouTube videos to find the bit that's relevant... awesome work!
Have you got any further plans to improve it, or just want to keep it simple?
To be honest I'd keep it simple and leave it as is. Just improve the landing page / chrome extension screenshots to have a more obvious value proposition / style. For me the video fails to load on your landing page.
Lovely app Ivan, also great job with the landing page.
One minor comment, I found the nav bar too squashed up at the top on desktop, maybe increase the padding, font-size and then also the Get Started button and you might increase conversion as well! Keep it up :)
I feel like there's a huge market for this, especially as it can be used so well by consumers a fun (non) disposable camera.
Lots of my friends have started buying disposables or point and shoot cameras as an excuse to solely take pictures and not worry about how they look until after they been developed. This is perfect for that, will start recommending it!
Tobias here. Seems like `homebrew/cask-fonts` is the best way to go for Homebrew, but even the repo maintainers suggest that submission to Google Fonts is their desired method to be included [1]. Once / if SN Pro garners more mainstream popularity we will start supporting more methods of distribution.
You can tell apart a capital "I" from a lowercase "L". The lowercase "L" has a tail on the end. Granted the capital "I" doesn't have a crossbars, but that's usually reserved for serif fonts, not san-serif.
The crossbars on the capital "i" are not serifs. Serif fonts have serifs on the crossbar.
Only sometimes does the lower-case L have a tail. And even if it does, there's no way to know that unless it happens to appear in the same text as a capital "i."
The vast majority of Sans Serif fonts do not use crossbars in the I[1]. But yes, we agree with you that it is important to distinguish the two characters, which is why we have, as Tobias noted.
But in what textual situations do you think it is important to have that clarity when the text does not have both characters? That's the situation where I think it is actually useful. If it is only one or the other, context should be sufficient.
I've attached a paragraph of text using SN Pro[2] that has copious Ls and Is of both cases. Please give it a read, I would genuinely like to know if you feel that our tails are not sufficient (not necessarily perfect, but sufficient).
Thanks for your reply. I’m on a phone at the moment but will check it out later.
In the meantime I’ll say that the ambiguous capital I is indeed rampant in sans fonts, but that’s not a reason to perpetuate it. Why have any ambiguity ever, when every schoolchild knows how to make a capital I? There is no benefit in doing so, and there are drawbacks.
Out of interest, have you had any problems with the AI hallucinating when generating new city guides?