Swiss Post Design System
swisspost-web-frontend.netlify.app
swisspost-web-frontend.netlify.app
I really appreciate government and publicly funded organizations open sourcing their work. Another example is Swiss Television and their apps[2] or government apps[3]. The public paid for it so they should also be able to benefit from all the work.
The Free Software Foundation Europe agrees: https://fsfe.org/activities/publiccode/publiccode.en.html
This doesn't happen in the corporate world (as much) because of various factors such as tax incentives and market pressures, but would be much more likely in the stately world of government IT.
A better solution would be license the code, such that it could not be used to provide public services unless the governing body contributed to a development association (either in money, code contributions, or some mixture thereof).
Only societies starved of ideas other than lowest common denominator free-market thinking. In reality societies choose to do the thng that cost money, for no other reason than that they want the outcome. We do tons of things for no specific (short term) gain. Some would say that this is what sets a great civilization apart from the rest.
Feels like a 4th wall break when something from your job pops up on the orange site.
> The DemoPage is an Angular App (SPA). But there is a lot of CSS you can use/run without Javascript.
And gfellerph, the lead dev, left the other comment.
(You can see the whole team at the bottom of the demo page)
The praise in this thread is clearly from people who never had anything to do with the modern Swiss Post.
I had to setup a mail "hold" order (in Switzerland you have to pay an extra fee and make a request to not deliver mail when you leave for a few weeks) and I found the UI to be very confusing.
I think the design of the site could be improved, here is what annoys me the most:
* The "clickable" button color being so close to the "disabled" color that it's very hard to distinguish when they are not next to each other (as most of the time) and very confusing when you try to click on a seemingly active button and nothing happens
* Calendar widgets letting you select every date, but after selecting the date, you get an error message
* communications in German despite the whole process being in French and the destination address being in a 100% French speaking canton
* downright bad French translation (hi from the 25% of the Swiss population) eg: "Reprendre" is *not* a valid button name, maybe use "selectionner"
* ending into a redirect loop when going back during the check-in step
The UI feels broken. There is a lot of "strange" space, or button layouts accidentally ending up on two rows eg: the login nag dialog (I could reproduce it on Firefox and Chrome).
It felt like a miracle when I managed to complete the process after about 1 hour (process that technically only requires my name, address and payment coordinates)
I'm used to computers acting up and generally bad software (hell, I use Linux), so I could handle it, but my mom says she has trouble with the website as well.
If you need more details, or a generous Romand QA tester, don't hesitate to contact me (domain of email address in my user profile).
I feel that good software is important, especially for a state-run monopoly. Because it's always the most marginalized people that end up eating up the hidden costs of rushed-up software.
* I don't work on the team of this demo itself, they are just part of my "Cluster" (unsure what it even is, yay to re-orgs). I am part of the Developer Platform team and am responsible for internal tooling (some dev, some ops).
* Postfinance and Swiss Post are mostly separate, though we share some things. I assume the design is one of those things.
* There is no one UI team, this page here is a demo of the Common Web Framework, which is managed by the CWF team.
But I will forward a link to you comment to the CWF team anyways, since they can probably do more with the feedback than me (if they haven't read it already).
v5.2 also moved a lot of the SCSS variables to CSS vars which is much nicer to work with.
- You can use this across different web technologies.
- You can use with off the shelf component libraries.
1. CSS architecture, making all the components inter-compatible with each other (very complex).
2. Accessibility.
3. Browser compatibility and responsiveness/mobile capabilities.
3. What components are you going to provide?
4. Documentation for the team using it.
5. Fixing all the bugs in it.
6. The _actual design_.
Bootstrap pretty much gives you 1-6. It makes decisions that are easy to criticise if you've got the resources of a big tech company behind you, but for most people, customising Bootstrap will let them focus on #7 and get all the rest pretty much done for them.
There are alternatives, taking any of the major CSS frameworks like this that has customisation built in will work, Foundation is another good one, but Bootstrap has a lot of the mindshare.
- Bootstrap JQuery
- Not going all-in on customisation with the built-in customisation options, but rather hacking on custom styles on top in our own stylesheets.
- Starting from Bootstrap 3.
I suspect that much of the hate stems from things like this.
Important to note that these organizations rely heavily on external contractors and small to mid-sized firms for their development. Making the tooling shared and accessible is probably a win on multiple levels.
If designers at these companies create "design systems" to have consistent UIs, why not aim for the ultimate consistency in UIs – whatever is standard in my computer?
Imagine trying to document your web app but it has 15 totally different UI appearances.
And I can tell you from experience with xplat tech like Xamarin.Forms, write once run anywhere with Native control appearances is a disaster, even in relatively controlled environments (limited to iOS and Android).
There's no such thing as standard controls between different sites today either.
But I'm certain there's more variation between sites than there's ever been between different browsers, and the variation between browsers is less likely to bother an individual user than the variation between every site in the whole web.
This is a "there's no single standard for browsers, so let's make every site unique" argument.
Even if they weren't making money, I would gladly pour my taxes on them because the level of service of say public transport here is completely priceless.