Mobile Banking Architecture Delivers Frequent, Revenue-Generating Updates
•
0 likes•4,097 views
MOBILE.UP - an extendable, pre-built mobile banking product which is also a development framework - providing faster development cycles: new releases every 3 months to keep up with your customers' needs. Contact us to learn more: http://wup.digital
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Mobile Banking Architecture Delivers Frequent, Revenue-Generating Updates
Similar to Mobile Banking Architecture Delivers Frequent, Revenue-Generating Updates (20)
Recently uploaded
Recently uploaded (20)
Mobile Banking Architecture Delivers Frequent, Revenue-Generating Updates
- 2. H.ELLO
- 3. FED-UP? Frustrated with delayed and over-budget mobile banking projects and change requests? Feel that you cannot catch up with frequently changing mobile trends and requirements? Your legacy IT infrastructure is not able to interface to innovative, real-time, 24/7 mobile apps? Reluctant to integrate an out-of-the-box solution because of vendor lock-in? Want to protect investments in existing digital channels platforms? Cannot show ROI and revenue generated from mobile apps?
- 5. W.UP - MOBILE.UP Implemented in 3 months, with releases every 3 months after that • Start with the basics • Add new features after 3 months • Add revenue generating features after 3months
- 7. END USERS IT SECURITYBANKS REVENUE AND GROWTH We designed an application with the purpose to engage with customers and generate revenue. RELEASE FREQUENTLY AND RAPIDLY The Holy Grail of UX is not functionality or UI, it is the ability to recognize customers’ evolving behaviours and react quickly. CLIENT DRIVEN INTEGRATION Our architecture has the ability to leverage legacy backend services and mask complex service calls to achieve a mobile optimized, instant and 24/7 service. SECURE BUT USABLE We balanced the most secure technologies and easy usability to create an experience where customers feel happy and secure at the same time. DESIGN CONSIDERATIONS
- 8. Simple, flexible, rapid client-side development and support of outstanding user experience CLIENT ARCHITECTURE Core Infrastructural services Common SDK for the function development Caches, navigation, secure data store, Communication Independent function development Separately designed, implemented and tested functionality Minimalizing effects between the components Seamless integration of new functionality Customization Documented API via Swagger End-to-end generated models and services Easy to modify the common classes during implementation
- 9. PUSH NOTIFICATIONS Adapters Implemented adapters to the providers Google Cloud Messaging Apple Push Notification Service Management API to external systems (post, status query) Messages conversion to the appropriate adapter format Recording status of messages Client-side Payload processing Navigation on functions
- 10. TECHNOLOGIES
- 11. SIGN IN. CHEER UP. Want to know more? Get in touch!
Editor's Notes
- Note down who is around the table!
- A Mobile.UP screenshot with 3 layers where the first layer contains the first implementation and the other two contains some visible functionality symbolizing the 2nd and 3rd release every 3 months. The layers need to indicate the releases. -Start with the basics -add new features after 3 months -add revenue generating features after 3months The slide should also contain: Our guarantee: 3.33 Mobile.UP Implemented in 3 months, with releases every 3 months after that
- Egy nagyon sematikus banki architektúrát láttok it: Alul vannak a legacy és a core szolgáltatások – ezek változtatásainak a életciklusa években mérhető. Efölött van egy szolgáltatási és middleware réteg – itt sem túl gyakoriak a változtatások, hiszen sok rendser használja ekezet Ezért kell erre felhúzni egy Omnichannel vagyis csatornákhoz kialakíttot API gateway és szolgáltatás réteget, amely az alap szolgáltatások használja, de a csatornák felé és third parzty fintechek felé verziózottan biztosít szolgáltatásokat még pedig modulárisan. Ennek a változás menegementje már lehet hetente.
- 7
- Out side those which are listed in the previous slide the following things are important: Mobile.UP Common SDK: using this the platform is open for third-party development, so even the bank’s can develop new functionality into the platform. Lot of services are provided with a proper documentation whichs should not be implemented during this development: common caches, security solutions, data storage, communication. Separate function development: no dependency between the functions, they can be put into the platform via the Common SDK. Via this approach it is also possible to integrate the solution with third-party solutions like different mobile-token, mobile PFM, chat, etc. Easy to customize and fast implementation: not just the Common SDK helps a lot for fast delivery, but that each of the interfaces and models are defined using YAML models on gateway side (also in component and versioned based way). The API-s and models are used by the clients as a dependency, which means that the client developers should not handle the communication issues and model generation issues, they can use the generated services immediately. With this approach the changes between the interfaces can be handle much faster and easier way. The client developers are not depending on the gateway side’s implementations, they can concentrate to the client side development only.
- Push notification engine: This is part of the W.UP Business Services, where the components are separate and can be used out-of-the box in a cloud based solution as software as a service, but they can be deployed and configured into an on premise infrastructure also as standalone web applications. Each component has a well-defined and versioned API which is by default a REST base solution, but other communication facades can be customized to them: like MQ, JMS, Soap over HTTP. This component provides and easy solution for mobile applications to handle push notifications. The solution is preintegrated with the Apple and Google cloud services and provides notification tracking solution for the sent out messages.
- The used technologies: This slide is important to show that in each platform (android, ios, gateway) we are using the widely used standards (and not the same everywhere). With this approach it is possible to minimalize the learning curve and with this approach it is much easier to keep the compatibility with the future mobile os versions.