I had designed WatchCamRemote prior to the release of the first Apple Watch. Understanding that the release of a new Apple product would direct a lot of eyes to this market- I had to dive in! The release of the Apple Watch also carried with it the exclusivity of it’s own independent app store. The exposure advantage of this independent store increased chances of greater exposure of early adopter apps as it’s market was independent from the billions of apps within the saturated iOS app market.
The concept was fairly simple. Users could utilize the watch and phone to observe, monitors, and be notified of actions taking place outside of their current environment. Specifically mimicking the functionality of video baby monitors, remote wildlife capture cameras, and extreme sport self capture cams.
Two basic types of functionality were needed for most of the image & video capture modes.
Initial concept designs conveying app functionality.
UI Information Architecture
Highly customizable settings were made simple and easily accessible via visual organization and graphical indicators providing cues to users.
After working through initial app designs and wireframes I ran into a major development issue.
Apple WatchOS does not allow for the selection of which device is to display push notifications. By default, if the phone device screen is active, Apple assumes that the user is viewing the screen; and therefore displays incoming notifications on the phone only. My concept intended for the phone’s camera to be operating and send push notifications to the watch as the phone screen was active. Without this ability accessible within WatchOS, I had to shelve the project until the native OS supports selection of the device to display notification. To be continued…