801269 - [meta] Include SIM Application Toolkit apps in the settings application

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::Settings, defect)

Description

[Marcelino Veiga Tuimil [:sonmarce]]

Here is the definition of all the functionality related to STK needed to support VIVO requirements. It was split in other Bugzilla tasks in order to be implemented incrementally, so just follow dependencies to find all the tasks.

User Story:
* As a user, I want to see all the SIM Application Toolkit apps in the settings application.

Acceptance Criteria:
* There is an option in the "Settings" menu called "Operator Services" when clicking there, all the applications available in the SIM Application Toolkit should be shown in a list.
* When a SIM Application Toolkit is launched by the platform, it needs to display a basic User Interface.
* That User Interface has not been build and should be created based on the building blocks that are available so far.
* There are some information about current implementation in https://wiki.mozilla.org/WebAPI/WebSTK.
* These are the command to be implemented:
  * REFRESH: enable the device to be notified of the changes to the SIM configuration that have occurred as the result of a SIM application activity
  * SET UP CALL: set up a call
  * SEND SS: send an SS (Supplementary Service) request immediately, without need to alert the user first
  * SEND SMS: send an SMS (Short Message Service)
  * SEND USSD: send an USSD (Unstructured Supplementary Service Data) immediately, without need to alert the user first
  * SEND DTMF: send a DTMF string after a call has been successfully established (depends on https://bugzilla.mozilla.org/show_bug.cgi?id=793137)
  * LAUNCH BROWSER: browser request content using the URL
  * DISPLAY TEXT: display a text message and/or an icon  (UX recommends to use a spinner to be stopped with this command)
  * GET INKEY: display text and/or an icon, and to expect the user to enter a single character
  * GET INPUT: display text and/or an icon, and any response string entered by the user shall be passed transparently to the SIM and shall not be stored in the device
  * SELECT ITEM: the SIM shall supply a set of items from which the user may choose one
  * SET UP MENU: the SIM shall supply a set of menu items, which shall be integrated with the menu system (or other MMI facility) in order to give the user the opportunity to choose one of these menu items at his own discretion
  * SET UP IDLE MODE TEXT: the SIM shall supply a text string, which shall be displayed as an idle mode text
  * SET UP EVENT LIST: the SIM shall use this command to supply a set of events, that shall become the current list of events to monitor (depends on https://bugzilla.mozilla.org/show_bug.cgi?id=790543 and also on https://bugzilla.mozilla.org/show_bug.cgi?id=795209 to get initial events)

* For testing this functionality, firstly we need a set reference STK applications to test all de commands implemented, and then we have to test all the applications installed in VIVO SIM cards.

Comment 1

[Marcelino Veiga Tuimil [:sonmarce]]

Implementation was already started before feature freeze and most of the commands implemented and merged. We need to finish implementation of remaining commands as it is a requirement for VIVO, so it needs to be blocking-basecamp+.

Comment 2

[Dietrich Ayala (:dietrich)]

We don't block on meta-bugs, only bugs that contain work that will take engineering time.

Comment 3

[Dietrich Ayala (:dietrich)]

Also, we're not blocking on late feature work. For the STK commands that didn't make it in, please follow the procedure for landing late feature work:

Once a patch is available, has unit tests, has code review, and has been confirmed to pass the smoketest, you can ask Vivien for approval to check-in the code.

Comment 4

[Marcelino Veiga Tuimil [:sonmarce]]

(In reply to Dietrich Ayala (:dietrich) from comment #2)
> We don't block on meta-bugs, only bugs that contain work that will take
> engineering time.

Sorry, I did not know that rule. Anyway the purpose of this issue is to describe all the functionality related to STK in a single place, so we do not get lost in small implementation tasks with no context around.

Comment 5

[Marcelino Veiga Tuimil [:sonmarce]]

(In reply to Dietrich Ayala (:dietrich) from comment #3)
> Also, we're not blocking on late feature work. For the STK commands that
> didn't make it in, please follow the procedure for landing late feature work:
> 
> Once a patch is available, has unit tests, has code review, and has been
> confirmed to pass the smoketest, you can ask Vivien for approval to check-in
> the code.

OK, we will do it that way

Comment 6

[Borja Salguero [:borjasalguero]]

Could we add it the same functionality to FTU App?