Is that hard to check the data back then, see what went wrong, create a new driver and help us out? I'm not a pro in soFtware things ,but I don't believe this is a VERY VERY HARD thing to be solved. I have found a post were a guy purchased a new keyboard and after few days the problem came back. to see if anybody with this problem got a reply with a solution, but nothing. There are people with new laptops that have this problem, I've been reading pages 1 to 100 in search of a solution. you have to spam them or use them with shiFt to work " like for me is F, G and SPACE ", they work but not all the time when I press them. There are quite a lot of people with this problem " some keyboard keys don't work every time you press them. You guys didn't fiGured this out yet, or you just simply dont want to help us? I had to create an inferior experience than I would ever have to for a native app.Since october 2017 when this problem appeared for few msi laptop models. I can't support my vision for what I originally wanted for those apps. There's a huge difference between what I could do with a Web App and what I could do with a native app. My programming projects taking the longest and most time consuming at the moment are all web based. That leads to either spending less on the man hours wasted subpar optimizing for lil Jimmy's Moto Z and Sally Sue's iPhone 7, or more work put into developing new features or products.Īre you a fucking programmer? No? Damn straight you're not. The only things holding those sites back are:Īlternative reason: A webpage can be as complex and functional as a native app, and it requires less work to port over to additional ecosystems. Websites have become increasingly complex and their functionality has expanded to be able to perform many tasks that would have required dedicated programs to run half way decent 15 years ago. Sounds like you spoke to a close minded dolt, whose probably old and set in his ways.
Many businesses still runs on Windows 7 (although they are indeed switching to Windows 10), it would make no sense for an app like Slack, which the whole point is that no one is left behind and it runs on anything, to drop support, or provide an inferior app experience to Windows 10 /10 mobile, due to starting fresh, and time is needed to catch up to the Win32 app feature set and quality.
At least, they expand their market share with Windows Phone 8 which actually has a larger market share, and on the PC side, their app being Win32, allows Windows XP, Vista, 7, 8 and 10 users use their apps (well today: Windows 7, 8 and 10). It makes 0 sense to make a native app for the platform. Let's be honest, with current market of Windows 10 Mobile, thanks to Microsoft wonderful efforts in pushing this platform since day 1. Sure it isn't a native Windows 10 UWP app, but it still delivers. They probably use something like Xamarin, allowing the core to be coded once, and delivered on all platform.
Definitely has some Windows 8/10 Phone/Mobile fans in the company. The app is feature complete and you should be happy that it is actually actively supported.
It feels like a web wrapper but it isn't, it is a native Windows 8 Phone app (so there is your loss of performance). It's so asinine that they can even get away with stuff like this.