to expand on this for anyone that isn't aware; most front-end teams are rapidly converging on using systems like React-Native / Flutter / Ionic; which allow you to "write once, deploy anywhere" e.g. mobile web, mobile app, desktop web, embedded / PoS, and sometimes tablet and watch.
This is possible by abstracting the layout engine (generally to match a web browser) and having UI control running in transpiled JavaScript.
In more practical terms, this means its easier to have one team managing your website and mobile app, reducing the number of specialist roles and minimising feature disparity. Generally it saves on duplicate work as well and makes timelines easier to manage.
For banks specifically there are a bunch of wins with respect to only having to ensure legal compliance of one application; this applies to banking laws - where certain information must be communicated at certain points, and to public accessibility laws. Most of these frameworks have a lot of tooling around language support and accessibility integrations.
So even if these experiences are inferior, it is very much worth it to the providers.
This is possible by abstracting the layout engine (generally to match a web browser) and having UI control running in transpiled JavaScript.
In more practical terms, this means its easier to have one team managing your website and mobile app, reducing the number of specialist roles and minimising feature disparity. Generally it saves on duplicate work as well and makes timelines easier to manage.
For banks specifically there are a bunch of wins with respect to only having to ensure legal compliance of one application; this applies to banking laws - where certain information must be communicated at certain points, and to public accessibility laws. Most of these frameworks have a lot of tooling around language support and accessibility integrations.
So even if these experiences are inferior, it is very much worth it to the providers.