AaronGustafson’s avatarAaronGustafson’s Twitter Archive—№ 17,445

      1. …in reply to @windowsdev
        @windowsdev I think it really comes down to taking an honest account of what your project’s goals are, it’s technical needs, and the skills of the team slated to build it.
    1. …in reply to @AaronGustafson
      @windowsdev If you are building a cross-platform app that supports Android, iOS, and the web in essentially the same way, it would be foolish to invest the time and money creating bespoke solutions for each. PWAs let you double down on your investment in the web.
  1. …in reply to @AaronGustafson
    @windowsdev But the reality is that not all APIs offered to native apps are available to the web. Many are, but not all of them. So in instances where your project absolutely requires access to APIs like that, native makes more sense.
    1. …in reply to @AaronGustafson
      @windowsdev Similarly, if your app is resource-intensive, native would also be ideal because it puts you one step “closer to the metal” in terms of raw processing power.