They didn't take ownership, they just paused decision-making and now major choices can veto'd by the ministry of economic affairs if they are deemed not in the interest of the Dutch company (which is part of a larger Chinese holding).
Isn’t Apple already in China? There must be a reason why they are not selling much there already, but perhaps they could dump prices and increase marketing. Although China and US is in a trade war right now, so prices are more likely to increase as China increase import taxes to balance ones the US has put on imports from China.
> I have never seen cross-platform UI that would work and/or look close enough to native.
But wouldn't knowing that require that you investigated the tech choices of all the apps you are using? If not, there's a slight fallacy in that you only _know_ that the app is cross platform when you can see that it is. So then obviously all the apps you know is cross platform will look out of place, because that's how you know they are cross platform. Not sure I'm making the argument very well.
For instance, I'm don't think that the Discord app for iOS and Android looks out of place [0].
> Switching to React Native for the Android app means an experience that is ever-improving at a more rapid pace across every platform Discord is available on, while still retaining Android and iOS specific patterns in the UI.
The discord user complaints rose exponentially after the switch to RN, and almost all users felt a perceivable difference in the quality of the new apps.
Hehe, I guess I was too late to party to experience the good ol' days.
It has a good rating in app store today. Better than Slack, even. And although there are probably many reasons for that, atleast RN hasn't killed the ratings.
this is quite normal when you do a full codebase refactor, even if you didn't switch technologies
it is like comparing a 5 year old codebase with 1000s of man-months ironing bugs out with a 1 year old codebase with 500 man-months of work
Seems like the bigger problem is their QA department than their engineering decisions
> But wouldn't knowing that require that you investigated the tech choices of all the apps you are using?
I did investigate every app I ran, because I was programming UIs and was interested in all tech that was there. To the point of being able to tell whether the app was written with Delphi or Qt or MFC/ATL by just playing with it.
Qt apps on Mac always stand out, being "OK" is the top they achieve.
Windows is less offended because it has never had a stable style, but still, there are always tiny details like context menus or not responding to Ctrl+Arrows that give non-native away.
It's not tricking, but it is deceptive since they haven't chosen to submit. The current mental model of forms are to save data entries when you actively submit.
Yes, there are some settings panels that automatically save changes, but I have never seen it for forms.
If there's an submit button on that form then that would be an even stronger signification to the user that nothing will be sent to the servers until you click that button.
I searched for something similar. Considered Caddy and Nginx/Apache with markdown plugins, but wanted to be able to create and edit pages/files and made a small script with Flask instead.
Maybe. But time zones are difficult for remote teamwork, and crossing borders also have legal, language, culture and tax issues. Many remote positions on job boards are “US only”. Perhaps for these reasons.
