It's now 2017 so this is much easier than in 2012.
Start with either:
Both are free to start, well documented, capable in the long term. As you get started in what you need, then look to see if perhaps a different single solution or combination of solutions makes sense for your budget, number of devices, and skillset(s).
For those interested in how it was in 2012 and the next several dozen months, it was a bit harder to manage iOS since the tools and iOS itself didn't have the hooks and maturity for this function. Then, the least expensive way to manage iOS mobile devices is to use the iPhone configuration utility. It is free, runs on Macs and Windows PC and you can email and host the configuration profiles on traditional web and file sharing solutions. I'm amazed it's still called the "iPhone" utility since it long ago became the iOS configuration profile utility.
The free support method would be FaceTime and iMessages and you can have your users take advantage of Apple's free tutorials, guides and retail worships and training. Past that, some businesses prefer to enroll in Joint Venture for training where your core team can get personalized business level training from Apple.
The next level of mobile device management would be Lion Server or one of the pay as you go MDM solutions like Robot Cloud where you can get started with MDM for $5 a month before deciding if your workplace needs the extra features of a full management suite like JAMF Software's Caspar Suite or Mobile Iron type solutions.
Whether you use profiles made by the Configuration Utility or a server based solution that hooks into Apple's Push Notification Service (APNS) so you can push remote wipe and remote updates to the devices in the field - all of these MDM solutions use the built in iOS management hooks and have various costs and expenses to acquire, learn and automate controlling change to 10 or 10,000 iOS devices.
Start small, and consider that your users will be highly motivated to learn on their own. You will want to make sure you have open feedback channels and learn from them. iOS deployments generally are less IT headache than many expect and much of the learning and support can be self-paced, on-demand and as needed. Getting iPads into the hands of the decision makers and support people months ahead of a wide scale deployment is critical to remaining nimble and avoiding making decisions before you know how the devices work in your work environment. Small pilot programs are also ideal to measure and adjust deployment when you are unsure how you will ultimately be managing these devices. Hang on, iOS deployment is a fun ride.
I'm pretty sure you can do this with a hot-corner and the built-in VNC server. (You would need a VNC viewer for iOS, there are LOTS of them.
You could also create an applescript:
tell application "System Events" to sleep
and run it using the VNC connection.
Alternatively, you can turn on ssh, ssh in, and issue the command:
pmset sleepnow (See the pmset man page)
to put the mac to sleep.
This would require a ssh client for iOS. Again, there are a LOT of them. Personally, I have used iSSH, and it works fine.
As @mankoff stated in a comment, RowMote states in it's store description:
- SLEEP AND WAKE: Put your Mac to sleep by holding the Play button for 3 seconds while controlling any Apple application, just like the
hardware remote. Rowmote automatically wakes up sleeping machines
which are connected via Ethernet!
Best Answer
All iOS SDK apps work within a security sandbox, and thus have no access or control over any other apps (with a few tiny exceptions for registered URLs). You could take control of you own app, but no others, including Apple's, on a stock OS device.