- 1. Test on your selected devices – I’ve seen a number of mobile developers forget this important step. Remember, mobile computers don’t have the same computing power and memory that a normal computer does.
2. Ask for feedback from the experts….your END USERS – Don’t forget to ask for feedback from the field workers that will actually be using the mobile application. It doesn’t matter what the application does if the mobile worker isn’t able to use it successfully. Simple is better, so plan ahead.
3. Take the time to train your team – Not everyone is as familiar with technology as we’d like. Someone needs to help others understand how to operate their new device (even how to turn it on). Going from a paper work order with a 2 way radio to a mobile computer with a wireless work order system is a paradigm shift so plan ahead. Even better, create a user guide for them.
To learn more about how MobileFrame can help you and your team with a successful mobile implementation contact us today.
Dont forget to register for our Webinar on April 21st – Here’s the link to register – ClickToRegister
Contact Us | Phone: 408.885.1200 | Email: info@MobileFrame.com
March 26th, 2010 at 11:26 am
Great points for success for AIS to remember as a VAR new to utilizing MobileFrame as a strategic ISV
March 31st, 2010 at 11:13 am
Hi Paul,
Thanks for the comment! Happy to have you as a partner!
Best,
Nick
April 21st, 2010 at 11:00 am
Extending your first point, it is important to test the solution with different OS versions. Be ready to experience surprises there.
Secondly, if the solution involves communication support it is important to test the software with WiFi, LAN, ActiveSync, GPRS/3G, with special focus on performance as some networks can be quite slow.
May 4th, 2010 at 5:44 pm
Onkar those are great Points!
Thank you for sharing!
Best,
Nick