![]() The lure of C# gets you into mobile dev, and you will learn iOS and Android in the process. it's probably a bad move.įor msft devs (and we are aging) it's win-win. For app-centric startups, games, POS systems, etc. NET and a simple cross-platform designer. They can throw a switch and restrict 3rd party runtimes if and when they choose.įor businesses in the 5-100 million range, writing an expense app in 2017, MSDN Xamarin should be a logical choice - but it has to be a platform with the reliability of. ![]() The build/release process is and (presumably) always will be locked behind the gates of technology's North Korea (Apple). Despite noble effort, the iOS design essentially needs to be done in xcode (point 4 above). Microsoft Universal Windows Platform Expert Bundle 1 Review 429 Enrolled 45 Hours 39.00 3,300.00 You save 98 - Sale ended 263 Lessons (45h) PowerShell Training Course Windows 10. The bulk of work is in the interface and navigation which is, necessarily, handled by coding android / ios specifics. Able to use device specific capabilities and adapt the UI to different device screen sizes, resolutions, and DPI. Able to use a common API on all devices that run Windows. Note: Microsoft employee but definitely only speaking for myself here.Īs a Xamarin subscriber, I'm guessing the future success of the merger (and product future) depends on:ģ) retaining the top engineering talent at Xamarin,Ĥ) addressing the iOS designer-specific issuesįor most LOB apps, I'm not convinced the code re-use is significant. A UWP app is: Secure: UWP apps declare which device resources and data they access. When those technologies hit mainstream browsers, great! Microsofts Universal Windows Platform is not dead, but it has evolved over the years By Daniel Rubino published 11 November 2019 Microsofts one-app theory for all devices is not as critical. I was always firmly in the first camp, and from that side of things I wouldn't take back a minute I spent on Silverlight dev - I got a jump on video, vector graphics, browser-based apps, etc., long before it was practical to do that in the browser. There were always two camps in the Silverlight world, both inside and outside of Microsoft: those that saw it as a way to make browser-based applications more awesome, and those that saw Silverlight as a way to get away from that yucky HTML/CSS/JS dev. If it had been my say, I'd have kept it for a little longer than they did, but by now I'd say it's no longer necessary. The JavaScript language and runtimes have matured considerably since then. all stuff that was pretty hard to do back then, but is now widely available in all modern browsers.Īlso, both the JavaScript language and runtime were pretty hard to build reliable, performant apps in back when Silverlight was introduced. I did a ton of work with Silverlight - streaming video, vector graphics, cross-platform front-end apps with back-end integration. Silverlight was essentially a polyfill for back when browsers weren't very capable.
0 Comments
Leave a Reply. |