Bank using WPF on ATM
Tim Heuer blogged about Wells Fargo adoption of WPF into their ATM user interface. For any technology, having a financial institution to adopt it in a customers facing application is really a vote of confidence that it is ready for critical mass.
With banks automating more of their businesses and putting them onto ATM and Internet banking, user experience is getting more crucial because of the dozens of services they offer, the screen property is limited. Old style ATM UI consist of just text is not usable to get customers to the service they looking for. WPF fits nicely here because of the deep integration with a strong application development platform like .NET and there is a good workflow synergy between the developers and designers to help boost productivity.
I just hope my local banks in Malaysia will realize this also and start putting investment into user experience around ATMs and Internet Banking.
3 Responses to “Bank using WPF on ATM”
RSS feed for comments on this post. TrackBack URL
Leave a Response
about me
Hi there! My name is Patrick and I code on .NET and build a few products on SharePoint and Windows Azure. I am currently CTO of IPS Infonomics Pte Ltd and co-founder of Tech Insights Conference.
My reading list- How to Deliver a Killer Business Presentation
- 10 Hot Web Startups Changing the Face of Retail
- Visa certifies NFC-equipped Android, BlackBerry smartphones for payWave -- Engadget
- An easy way to use certificates for WCF security - CodeProject®
- 6 Things To Do when you got your Unifi Wireless Router D-Link Dir-615 « Sawanila.com™
- Controlling Registry ACL Permissions with Powershell
- Building the Ultimate SharePoint 2010 Development Environment
- Running SharePoint 2010 on a domain controller
- Using Local Machine Accounts for Managed Accounts in SharePoint 2010
- How Trello is different - Joel on Software
< ![CDATA[I am software developer in Kuching. One of my client needs a retail kiosk application, which I made it in WPF. Frankly speaking, WPF application is low and taking too much memory, which require better PCs to run a WPF app. I doubt local banks will invest so much to upgrade PCs just to run better styled ATM application....]]>
Comment by — June 20, 2008 @ 12:24 pm
< ![CDATA[cccchai has point there.
another point to consider is. The front-end might be WPF but i m not sure whether the back-end process will turn to .net though. Considering the performance cause
compare to other proven technology
But wht do i nkow..i m just a small potato :p
Just an opinion
cheer
p.s great infor on .net product though.
btw.. ijust a feedback, i have nseen all ur post :p maybe u could put in some info on tech other than msoft :P ...since this is ur personal blog]]>
Comment by — June 20, 2008 @ 5:00 pm
< ![CDATA[wpf 3.5 sp1 will tackle some of the mentioned performance issues. on the mean time, as the blog title, the bank only uses WPF on the backend. yup it is true that a lot of banks will still be using mainframe to their backend, but isn't it wonder to migrate or upgrade your technology part by part?]]>
Comment by — June 24, 2008 @ 2:34 pm