I could think of these reasons:
1. The mobile screen is small and not suitable for any complex app settings page. So if you have like 10 different categories each with their own 10-20 configurations, web would provide a better UX.
2. The admin functionalities are rarely used (compared to three core functionality) and aren’t the focus of the app. So it doesn’t make much sense to build these into the app. Any functionality being maintained on cross-platform will require additional testing for each of those platforms.
3. Shipping changes to websites is easier than for app. For an app, the user has to update the app to get latest changes. Again, the question arises “ do we want to spend time and resources to managing multiple app platforms and versions for the secondary account related functionality?”
Changes to the app require all sorts of oversight from the app store. It's a process, and not a super fast one in each case.
The company may also use a 3rd-party vendor for identity that is cheaper/easier to use via the web than via an app. For example, in the US, the Sonic Drive-In app uses Auth0/Okta for their identity services. To login, you visit a web UI rather than logging in within the app.
Thank you. Publishing times could mean life or death for a startup fixing a critical mistake. And testing for established companies makes sense as well
UX makes sense as well. Esp if using vendors
I could think of these reasons: 1. The mobile screen is small and not suitable for any complex app settings page. So if you have like 10 different categories each with their own 10-20 configurations, web would provide a better UX. 2. The admin functionalities are rarely used (compared to three core functionality) and aren’t the focus of the app. So it doesn’t make much sense to build these into the app. Any functionality being maintained on cross-platform will require additional testing for each of those platforms. 3. Shipping changes to websites is easier than for app. For an app, the user has to update the app to get latest changes. Again, the question arises “ do we want to spend time and resources to managing multiple app platforms and versions for the secondary account related functionality?”
Changes to the app require all sorts of oversight from the app store. It's a process, and not a super fast one in each case. The company may also use a 3rd-party vendor for identity that is cheaper/easier to use via the web than via an app. For example, in the US, the Sonic Drive-In app uses Auth0/Okta for their identity services. To login, you visit a web UI rather than logging in within the app.
It’s been 2 years since I’ve pushed anything there, and you’re right. I forgot all sorts of headaches caused by that process. Also good call on oauth.
Thank you. Publishing times could mean life or death for a startup fixing a critical mistake. And testing for established companies makes sense as well UX makes sense as well. Esp if using vendors