So you're better off generally to make the app a web app. If that doesn't work yet, are you sure about that? With web assembly and some new browser apis it's really very few apps left that actually need the native experience.
Sure if you build apps for cars, planes or something like that I understand that you want the native experience. But there is also tons of "native with an asterisk" tools like Xamarin and React Native for example.
Sure the app may be a bit larger but do users really care? With those kind of technologies you can build native for all platforms easily.
The choice really is up to the developers and there is lots of choices nowadays, thankfully.
I vaguely bought into the idea for a while and now github are like:
> Review PRs and look at code on a mobile form factor
and now I'm like:
> oh, so that use-case is a thing?
I'm terrified some CTO in twenty years time of an org we want to sell it to will instantly shitcan our offering because it doesn't support mobile use-cases. Because mobile is their culture and the reason we don't value it today is _only_ because mobile isn't the culture we grew up with.
Being a dinosaur and seeing a big fiery thing in the sky. Thinking maybe it'd be better to get a bit of a head start on that mammal business. But its hard to make that business case, isn't it? Thankfully this news makes it easier I guess.
I am most intrigued.
They're kind of strange, to be honest.
Perhaps the typical university path makes it less common? I'd imagine the autodidact path might be more likely for a new breed should the new breed even exist.
I had been trying to tell myself that people still "sit down at a desktop to do work" to make myself feel better about our inaction over this it but that github is spending on mobile form factor makes me feel like I'm lying to myself about that.
What are people's general takes on this? I sway towards "in twenty years it will start to be a massive deal" but I struggle to find a convincing platform to soapbox on this to the organisation at large.