So you need to build a mobile enterprise app that runs on Windows tablets…
Your app must retrieve data from SQL Server and take it offline. It must allow the mobile user to view, manipulate, capture new information, and then send it back to the data center. There’s lots of data involved, so you require a mobile database with easy-to-use SQL rather than writing your own file I/O code. While you could create dozens of web services, hundreds of web methods, plus associated data sync logic, you’d prefer to have that plumbing handled for you. Since you can’t count on ubiquitous networking, the app must work well in an occasionally-connected environment. Data transmissions must thrive in the slowest GPRS speeds and network dropouts must be handled smoothly via intelligent resume. While you’re super-excited about the new programming model in Windows 8, you need this app to work on your company’s Windows 7 tablets and laptops as well. Oh, and it has to work on those 32-bit, Intel® System on Chip (SoC) Windows tablets with long battery life. The app must have a touch-first UX that works with fingers on tablets while supporting a mouse on laptops. The sync technology must authenticate with your company’s Active Directory and both data-at-rest plus data-in-transit is encrypted. While the initial app deployment only runs in the thousands, the system architecture must scale out to support tens or even hundreds of thousands of tablets. Most of all, you’re looking for a simple solution that gets your app to market faster at a lower cost by avoiding developing everything from scratch.
If this sounds like your scenario, I’m writing your next book.