3 ms·
I too find this baffling. I have developed and maintain two platform native pairs of apps in use in the agriculture level irrigation control sphere. Our reasons
by travisgriggs 3y ago
I too find this baffling. I have developed and maintain two platform native pairs of apps in use in the agriculture level irrigation control sphere. Our reasons for doing so are varied (historical, user experience, performance, desire to minimize cloud dependencies, need to really push Bluetooth and other OS assets (like location, storage, and photos)). But it is a butt ton of annoying work. From Java to Kotlin, Android to Compose, ObjC to Swift, UIKit to SwiftUI. It seems to never end. How I would love to use the a “cross platform silver bullet”, but I spent 20 years using and pitching Smalltalk in that space and am just really distrustful that that problem is truly solvable. But I’m surrounded by what seems 10:1, if not more, of web programming hoards who all use the cloud and web apps as the hammer to every problem they see. Their enthusiasm through the industry is great. I honestly am confused why I see app after app be retooled native in parallel or in replacement to a mobile web app. The variety of contexts is great enough that I’m uncomfortable ascribing it to a machivelean subtext of control. There’s too much inconsistency and incompetence betwixt the various marketing/steering levels of all the participants to see it as some universal evil plot. I feel there has to be something more general going on.