Android development

Why is the Android developer experience and ecosystem so poor? It's crazy how complex it is to get anything done. There are so many edge cases built in, like config changes killing Activities and restarting them. There's no standardization or consolidation of app architectures. If you're applying for an Android dev job, you might end up working on a project with many God object Activities and procedurally-initiated UI, maybe instead XML views, there could be Fragments, it could be MVVM, MVP, MVC... Oh but wait, now there's Jetpack Compose too (it looks a lot nicer than the other approaches), but it's very new. And of course you have to choose between Java and Kotlin. How did a gazillion dollar company let their flagship platform get so fuarrrked up?

>>32313 Use a third party framework: Ionic, React Native or Qt. You can use a plethora of languages with the first two.

>>32314 That makes sense. If I was going to go into mobile dev, I'd likely try to get a job working in Flutter. It looks a lot more sane than native dev, though on the other hand, I suspect interop can be a pain in the ass. Once again though it's baffling: Google's cross-platform mobile UI framework is higher quality than their own platform's native toolset. What were they thinking?

Try obsidian/reflex so you can write it in haskell. That also compiles to ios and web, apparently. I'm going to start a medium sized personal project in reflex to replace an outdated app I use

>>32317 I would like to find good documentation for it.

>>32313 It's to keep indie developers from gaining too much power relative to megacorps; all this obligatory bloat keeps them dependent on official packages and update channels. Xamarin was pretty decent for its time (when it was still free and based only on Mono not m$ .NET), now Flutter does something near-identical except with another BS managed language, I worked with it for half a year and can't even remember what that YAML-looking stuff was called. In the end not writing your own foundations over the corporate swamps of proprietary CRUD is always going to lead to homosex, monkeypox, and your neighbors injecting their children with weaponised VAIDS. FOSS foundations can work if you learn to write native modules for them AND know how to build them yourself AND maintain archives of all relevant docs; otherwise they may he deprecated (as they always have been thus far) and then you're back in the swamp until you take over the entirity of maintenance of the deprecated projects, and you are NGMI if you're not prepared for that happening.

>>32331 Based schizophrenic rant.

>>32331 I don't think it's deliberate, all enterprise software becomes overly complex and bloated over time.

>>32337 >I don't think it's deliberate, people are literally spending all of their working lives writing complex bloated trash with their very own fingers, must be an accident/random/for no reason/an emergent result from a totally well-intended "enterprise" system that has consistently bad results due to no fault of anyone involved.

Flutter was released in 2017 but still only handful of jobs. I thought Flutter was going to be next big thing, what happened? I've couple of projects that needs to be finished in the couple of months before I start searching for my next job and I thought Flutter gonna save me, what gives?

>>32344 It's a commercial cross-platform toolkit; it gets abandoned, or in the case of commercial/proprietary toolkits, promoted on HN and then abandoned.

>>32313 >How did a gazillion dollar company let their flagship platform get so fuarrrked up? The answer is that they're a gazillion dollar company. Large corporations have tons of employees working on different parts of the same thing at once, most of which will never even interact with eachother. It's hard to keep things tight and organized when you're managing that many people.

>>32313 Yeah I think the same thing OP

>>32314 >>32317 WRONG you still end up needing to use and know the android ecosystem. its 2x as much work to learn the cross platform framework and android, you should learn android, ios, seperately then learn at most one third party framework, to see its not worth it. its the web development problem, where on a team of developers you either end up making a compatible framework or using one.

>>32331 Xamarin was fuarrrking garbage, i think it must have been designed by retards, if you wanted to make an image usable you needed to write a manifest file for the image in a proprietary language called XAML, every single fuarrrking step of writing a Xamarin application was comparable to having a soldering iron inserted into your urethra, i wanted to throw my fuarrrking laptop out the office window multiple times a day when i worked a Xamarin job