Happy Clouds Mobile App V2

Happy Clouds v2 | a mobile app for Cloud FoundryTM || Kristen Mozian

1

Happy Clouds Purpose: A mobile app that allows users to manage

and react to changes in app usage deployed in the

cloud

Goal: To create a minimalistic interface that prompts

direct action


2

1 4 3 2

1—4) On the home screen of Happy Clouds the user can add a cloud by tapping the icon of the cloud with the plus sign. The user must enter their credentials to add the cloud to the app. If the user chooses for the app to not remember the cloud’s credentials, they will have to log-in in order to access the apps and services in this cloud.


3

5) When a cloud is added successfully it is automatically displayed on the home screen of the app. A graphic of a cloud represents the cloud added with its given name displayed inside the graphic. Below the graphic, the numbers next to the symbols tell the user how many apps and services are deployed from that cloud. The box symbolizes apps and the gear represents services. The add a cloud button remains on the screen and moves to accommodate the added cloud. 5—8) Adding another cloud to Happy Clouds, this time choosing the app to remember the cloud’s credentials.

7 8 5 6


4

9) The add a cloud button remains on the screen and moves to accommodate the added cloud. 9—10) Logging into Cats and now choosing for the app to remember the cloud’s credentials. The user will no longer have to log-in to Cats. 11) This screen displays all of the apps and services deployed in Cats. The symbols denote if it is an app or a service, and its respective name is displayed under the graphic. 12) Choosing to view the app Cute Attack.

9 11 10 12


5

15 14 13

13) This is the dashboard for Cute Attack. It is separated into 5 main categories: memory, CPU, instances, clone, and alerts. In each of the categories, information is displayed. In memory, “set at” refers to the current memory capacity the app is allotted. “high” and “low” refer to the push notifications set by the user. When the app reaches 128MB or 64MB the user will be notified. Similarly, under CPU, “current” shows the user the current CPU, and “high” and “low” refer to the push notifications set by the user. In instances, “set at” shows the user the amount of instances the app is allotted. The clone button at the bottom of the screen allows the user to clone the app to a cloud already added to Happy Clouds. The alerts button next to the clone button will provide notifications when push notification criteria is met.

13—15) Instead of using the back button to get to the home screen of Cats, the user can simply scroll right or left to see all the app and services Dashboards.


6

16) This is the dashboard of a service. It tells the user what type of database it is and allows the user to unbind the service. 16—17) When the unbind button is tapped, a pop up alert box certifies the action by clearly stating what the user is doing. The option “yes, unbind” reminds the user the action they are about to complete. Re-adding the service can not be done on Happy Clouds. 18) Purr is removed from the Cats dashboard. Also, in the top right hand corner the number of services decreases.

16 18 17


7

19—22) The user can change the memory capacity at any time by tapping the “set at” field. The user can change the memory capacity to any of the standard prescribed options (64MB, 128MB, 512MB, 1GB, 2GB) by using an iPhone picker interface. After clicking save, the memory capacity information is automatically updated on the app’s dashboard.

19 22 21 20


8

23—26) The user can set push notifications on memory capacity to be notified if the app’s memory capacity is pushed higher or lower than desired. To set the notifications, the user taps either the “high” or “low” field. Both actions take you to the same screen, since seeing the information side by side allows the user to make quick changes on both settings. There is an “off” option on the interface for users who want to turn the notifications off. By tapping save, the information is automatically updated and saved to the dashboard.

23 26 25 24


9

27—30) Similarly to the memory push notifications, the user can set parameters to be notified when certain CPU rates are met. By tapping save, the information is updated and shown on the app’s dashboard.

27 30 29 28


10

31—34) The user can increase or decrease the amount of instances on an app by tapping the “set at” field under Instances, and scrolling up or down on the interface the appropriate amount of instances. The interface allows up to 20 instances per app. By saving the information, the app and dashboard are updated. Of course, the user can tap “back” in the upper left hand corner to cancel the action, and no information will be altered.

31 34 33 32


11

35—38) A user can clone an app to another cloud already added to Happy Clouds by tapping “clone.” The user is then prompted to indicate what cloud the app will be cloned to. By tapping done, once the action is completed an alert notification pop up saying that the app has been cloned to the designated cloud as the predetermined default name—the app name plus a number, in this case Cute Attack 2. When the user taps OK, they will be brought to the cloned app’s cloud dashboard. From there, the app can be accessed as any other app.

35 38 37 36


12

39) When a notification parameter has been reached, the app has heavy throughput, or has high latency, the user will be notified through notifications on the user’s cell phone interface (not shown) and on the app’s dashboard. 39—42) The user taps the alerts button to view the notifications. The next screen shows the list of notifications. The user can hit OK and the alert notification would still be shown on the app’s dashboard, or the user can fix it by tapping the notification. Then, the user will be prompted to fix it through standard prescribed means. In this case, increasing the number of instances could handle a great CPU rate. The user can decide to ignore the alert by clicking cancel (and the alert will still show on the app’s dashboard unless the CPU parameters change) or the user can tap next. When the user taps next, they will be brought to the interface to follow through with fixing the problem. In this case, the user is brought to the interface to change the number of instances.

39 42 41 40


13

45) Fixing a heavy RAM load scenario through either increasing instances or increasing memory capacity and choosing memory capacity.

43 46 45 44


14

49) Fixing heavy throughput by cloning the app to a different cloud, and then proceeding to be facilitated to take those steps.

47 50 49 48


15

50) Fixing high latency with cloning the app to a different cloud.

48 51 50 49


16

52) If an app is dead, the app’s symbol will change from a box to a skull and cross bones to signify to the user that the app is dead. 53—54) When the user views the app’s dashboard, all actions will be inaccessible. The user will only be able to tap the alerts button. The alerts notification page notifies the user the app is dead. The user will have to fix the problem on a non-mobile device. The alert notification will still appear on the dashboard until the problem is fixed.

52 54 53 54


17

55—58) To delete a cloud from Happy Clouds, the user taps the trashcan symbol in the top right hand corner on the home screen. The clouds will become highlighted with an “X” to the upper right of the cloud. The user taps the “X” to delete that cloud and is prompted to confirm the action, in which the user can confirm by tapping “delete” or canceling the action. After the cloud is deleted, the home screen updates the interface.

55 57 56 58

Technology

Happy Clouds Mobile App V2