So, I guess React Native can now mostly support all these. We'd ideally want to support the following platforms: So, now you're probably thinking: " Just use React Native, or Flutter, or Electron or some other meta platform!"īut that still doesn't solve it, for several reasons. But that doesn't mean it isn't a a lot more work. If you're like my big clients, maybe that's worthwhile. If you really "go all in" on native, you have to build at least three different code bases instead of one. Ok, let's look a little closer, maybe it's not actually so bad? so just build native apps for that, or use Electron. We keep running into these limitations of what the browser can do. This happens both in my consulting work (currently with Walmart, previously at Starbucks), and in my business. More frequently, this is becoming "you need to do something that Apple doesn't think the web should be able to do" (or won't prioritize the work required to implement). That's what I'm trying to do! But sometimes, you need to do something that the web does not yet allow. Cost effective and sustainable? Not really. Then, once everything is submitted, they will mail you a USB drive with the certificate on it.ĭoable? Sure.Submit/upload a bunch of documentation, including a formal attestation letter from your CPA (who obviously won't do this for free). Complete some really extensive information about your business.Buy an Extended Validation cert for \$349 (a year).If you want to provide a link to download an electron app installer from your site and you don't want to have to coach your users how to click through the Windows warnings when they try to run the installer you have to do code signing. for each platform.Īnd most of these little steps and requirements are different for every platform you want to distribute to. Every time you want to do a material update, you have to repeat this same silly song and dance again.Dealing with obsolescence due to platforms moving forward without backward compatibility.Risk of being demoted in the lottery of app store picks and search engines. that is unique to each platform you want to distribute to. In short, because software distribution is hard.Įvery other means of distribution involves a variety of B.S. Looking forward to the battery life benefits this API will bring.- othermaciej September 12, 2019 Ricky is a WebKit engineer and who responds with a similar attitude is currently head of WebKit Engineering: The following appears to be the general attitude I see from the Webkit folks even for adding something as benign as screen lock. This gives me a new hope for the future of The Web! Meanwhile over on IE, ahem. See it for yourself! goo.gle/fugu-api-tracker The web as an application platform, has an incredible future. In fact, there's an entire public spreadsheet with a really ambitious list of capabilities that have been identified as gaps between what the web can do and what native apps can do. If a native app can do it, the web should be able to do also! Progress!Īs it turns out the folks on the Chrome team feel the same.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |