u/tsoojr

https://pos.usecue.com/p/blog/a-checkout-without-commission/

So I live in the EU and I am sick of Google, Apple and the big PSP's earning money from our payments. They make millions because we want to buy stuff from each other. Madness! Therefore I created a modern payment method relying on SEPA Instant Payments (direct bank transfers that have no transaction fee and no middle man).

Do not think I promote this because I want users... I really don't (and my tool is free, so it would not benefit me either). The only thing I want is for you to understand how it works. Play with it. Explore it. Then build it yourself. Integrate this into your checkout process. It is a different but simple concept that you need to see to understand. I only want to show you that it is possible.

We should not need to pay big brother to buy stuff from each other! Nobody asked me for a euro or dollar when I paid with a 100 note. Why would we accept that now? Thank god we don't have to in the EU. Together we can cleanse the temple, just like Jezus did. Become a part of this new movement in which we make direct bank transfers the new standard.

#showofsaturday

Native <select multiple> has been a UX mess for ~15 years: hold-Ctrl on desktop, inconsistent on mobile, painful to style. I tried to fix it without reaching for a framework or a 150KB combobox library.

It's a small polyfill — drop in a plain native select, link the JS + CSS, done:

&lt;label for="fruit"&gt;Fruit&lt;/label&gt;
&lt;select id="fruit" multiple required&gt;
  &lt;option&gt;Apples&lt;/option&gt;
  &lt;option&gt;Bananas&lt;/option&gt;
&lt;/select&gt;
&lt;script src="multiselect.js"&gt;&lt;/script&gt;
&lt;link rel="stylesheet" href="multiselect.css"&gt;

What it does:

Native control on mobile (the OS picker), checkbox group on desktop
Native form submission + required validation still work
Supports <optgroup>
No JS? You just get a normal <select multiple>, so it degrades cleanly
Where the new customizable select (appearance: base-select) is supported, it steps aside and lets the browser do its thing

Honest open question, mostly for the a11y folks: on mobile I hand off to the native control rather than checkboxes. I'd really like screen-reader testing (VoiceOver / TalkBack) on that path — is it solid, or should it be checkboxes everywhere?

It's my own project, free and open (WTFPL), no tracking, no build step:
https://code.usecue.com/multiselect/

Curious what edge cases I've missed.

A free zero-commission POS and PSP

Accessible multiselect polyfill (checkbox group on desktop, native on mobile) — looking for screen-reader testing feedback