How to Understand Developing Native, Hybrid and Progressive Web Apps
creatorsneverdie.com
How to Understand Developing Native, Hybrid and Progressive Web Apps
1–10 of 10 posts
Re: How to Understand Developing Native, Hybrid and Progressive Web Apps
#2[deleted]
Re: How to Understand Developing Native, Hybrid and Progressive Web Apps
#3"It can take up to 2x-3x times longer to make an Android app" . Is this still true? Was it ever really true? I've seen android features tend to take a bit longer, but we're talking like 20% longer, 7 years ago. Now, in the age of kotlin/swift, better android tooling, numerous iPhone sizes/DPIs, the Notch™, etc, etc I think I think the playing field is pretty level.
Re: How to Understand Developing Native, Hybrid and Progressive Web Apps
#4"It can take up to 2x-3x times longer to make an Android app" . Is this still true? Was it ever really true? I've seen android features tend to take a bit longer, but we're talking like 20% longer, 7 years ago. Now, in the age of kotlin/swift, better android tooling, numerous iPhone sizes/DPIs, the Notch™, etc, etc I think I think the playing field is pretty level.
If you creating a hybrid app the apple app process takes longer (needs approval) and involves more resources (how much is an apple license these days last I checked it was 100 us)
Re: How to Understand Developing Native, Hybrid and Progressive Web Apps
#5"It can take up to 2x-3x times longer to make an Android app" . Is this still true? Was it ever really true? I've seen android features tend to take a bit longer, but we're talking like 20% longer, 7 years ago. Now, in the age of kotlin/swift, better android tooling, numerous iPhone sizes/DPIs, the Notch™, etc, etc I think I think the playing field is pretty level.
It might take that long if you’re doing extensive UI theming and lots of custom widgets, but relatively few apps actually need those things. Even accounting for branding, a solid color scheme paired with Material Design on Android and UIKit on iOS are mode than good enough for the vast majority of cases. Creating garden variety CRUD apps with pleasant UX doesn’t actually take that long; it’s doing backflips and cartwheels with design that’s time consuming.
Re: How to Understand Developing Native, Hybrid and Progressive Web Apps
#6"It can take up to 2x-3x times longer to make an Android app" . Is this still true? Was it ever really true? I've seen android features tend to take a bit longer, but we're talking like 20% longer, 7 years ago. Now, in the age of kotlin/swift, better android tooling, numerous iPhone sizes/DPIs, the Notch™, etc, etc I think I think the playing field is pretty level.
Matching UI to designs was horrible on Android, at least as of ~1.5yrs ago. Even if designers were shooting for "Material". Plenty of rough edges. I wouldn't say 2x-3x longer for a typical project, though.
I could see there being issues with relatively new-to-Android developers not appreciating the degree to which advice from the official docs, especially relating to structuring applications, should be taken with a largish dose of salt, leading to slow-and-getting-slower development as an Android project went along.
Re: How to Understand Developing Native, Hybrid and Progressive Web Apps
#7Good content but that eye-searing blue and custom cursor really bother me.
Re: How to Understand Developing Native, Hybrid and Progressive Web Apps
#8I only want to develop PWAs for now on. https://appsco.pe/
Re: How to Understand Developing Native, Hybrid and Progressive Web Apps
#9"It can take up to 2x-3x times longer to make an Android app" . Is this still true? Was it ever really true? I've seen android features tend to take a bit longer, but we're talking like 20% longer, 7 years ago. Now, in the age of kotlin/swift, better android tooling, numerous iPhone sizes/DPIs, the Notch™, etc, etc I think I think the playing field is pretty level.
Matching UI to designs was horrible on Android, at least as of ~1.5yrs ago. Even if designers were shooting for "Material". Plenty of rough edges. I wouldn't say 2x-3x longer for a typical project, though. I could see there being issues with relatively new-to-Android developers not appreciating the degree to which advice from the official docs, especially relating to structuring applications, should be taken with a l…
To get to the level of world class competitiveness i'd say it's true. if you want to compete with say instagram then android is such a PITA to design for.
As for your second point, i've always followed the official docs,are you saying there's another way?
Re: How to Understand Developing Native, Hybrid and Progressive Web Apps
#10Earlier quoted context omitted.
Matching UI to designs was horrible on Android, at least as of ~1.5yrs ago. Even if designers were shooting for "Material". Plenty of rough edges. I wouldn't say 2x-3x longer for a typical project, though. I could see there being issues with relatively new-to-Android developers not appreciating the degree to which advice from the official docs, especially relating to structuring applications, should be taken with a l…
To get to the level of world class competitiveness i'd say it's true. if you want to compete with say instagram then android is such a PITA to design for. As for your second point, i've always followed the official docs,are you saying there's another way?
Square's guides and libraries in particular were a great place to start when last I worked on Android (2017). They filled in a lot of dumb gaps in basic, common functionality, and their guides and blog posts on Android topics generally left me feeling more confident in them than in Google's Android team. They were among the ones calling "the Emperor has no clothes!" over fragments, for instance, and they described and built alternatives.
It does look like they've abandoned a couple of their big view-related Java libs, which makes me wonder what they're using now. Seems they've switched to Kotlin for a lot of stuff.
Don't remember their blog being on Medium (ick) but it is now, looks like: