this post was submitted on 24 Jun 2024
441 points (98.0% liked)
Asklemmy
43939 readers
1047 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Department lead.
The website team is small, but incredibly effective. Everything works. Everything is mobile friendly, responsive, fast. It's a way better experience.
I love my app developers, but they're always behind. Not their own fault. Mobile development is complicated. There's so many screen sizes, iOS vs Android differences, platform permissions, etc.
The big reason for us to push the App on people was to get more brand awareness on the App Store. But the website is so much more better.
You literally can use it as a web app right into your phone and get a better experience.
And it'll be such a dark day when I have to dissolve the App team (and hopefully convince them into web dev)
Why not a responsive web app packaged into native viewer app? Depending on your utilization of native components of cause.
My team had the same issues you described so we build the web responsive and made that the "Apps" on the App Store + Google Play. There is still a tiny native components that hook into the web so you still need those native developers knowhow, but yes they will have to switch in large to web based development.
Less maintenance, more devs for the main product, faster progress, fewer headaches with Apple and Google tooling.
Edit: forgot to app that our customers loved that more features are available now on the "Apps" and that things work the same between devices
But where is has the compromise happened? The Kotlin/Flutter/swift code written? The database? not being sarcastic just unaware.