Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2026

Improve submit app confirmation page to better inform user what is happening

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Story Points:
      2
    • Sprint:
      Fall 4 : 30 Sep to 11 Oct, Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov

      Description

      When developers upload an App, App Store must perform first-level automated review of the App to make sure it follows basic specifications. For example:

      • Jar file must contain OBR index file called "repository.xml" at the top level of the jar
      • Jar file MANIFEST must contain OSGi headers of Bundle-SymbolicName, Bundle-Version, and Bundle-Name (note that Bundle-Description is optional)
      • An uploaded jar file can have the same Bundle-SymbolicName and same Bundle-Version as a currently "pending" App, but not a released App
      • An uploaded jar file can have the same Bundle-SymbolicName as a released App but its Bundle-Version should be different

      All the various combinations of what a developer can do are kind of complicated, and our current submit app feedback page does not do a great job of explaining what's happening when a developer submits an App jar. For example, we are telling the developer whether the uploaded jar file is a "new app," but there are several ways that an App can be new!

      Let's change the feedback page as follows:

      Instead of displaying the line: "Is the is a new App" and then showing either "Yes" or "No", let's instead display a different line: "App Summary" and provide some text explaining what we think the developer is doing. If the developer reads this text, they will be able to decide whether to proceed with the next step of either canceling the submission or proceeding with submission.

      For the new design, please see this PowerPoint:

      https://www.dropbox.com/s/xe1v2jo17fg23th/SubmitApp-JarUpload.pptx?dl=0

      (This is the same PPT as for IGBF-1995, but with new slides added.)

        Attachments

          Issue Links

            Activity

            ann.loraine Ann Loraine created issue -
            ann.loraine Ann Loraine made changes -
            Field Original Value New Value
            Epic Link IGBF-1388 [ 17463 ]
            ann.loraine Ann Loraine made changes -
            Link This issue relates to IGBF-1955 [ IGBF-1955 ]
            ann.loraine Ann Loraine made changes -
            Rank Ranked higher
            ann.loraine Ann Loraine made changes -
            Assignee Ann Loraine [ aloraine ]
            ann.loraine Ann Loraine made changes -
            Resolution Unresolved [ 10101 ]
            Sprint Fall 2019 Sprint 3 [ 74 ] Fall 2019 Sprint 4 [ 75 ]
            ann.loraine Ann Loraine made changes -
            Status Open [ 1 ] To-Do [ 10305 ]
            ann.loraine Ann Loraine made changes -
            Assignee Ann Loraine [ aloraine ]
            ann.loraine Ann Loraine made changes -
            Description When developers upload an App, App Store must perform first-level automated review of the App to make sure it follows basic specifications:

            * Jar file must contain OBR index file called "repository.xml" at the top level of the jar
            * Jar file MANIFEST must contain OSGi headers of Bundle-SymbolicName, Bundle-Version, and Bundle-Name (note that Bundle-Description is optional)
            * An uploaded jar file can have the same Bundle-SymbolicName and same Bundle-Version as a currently "pending" App, but not a released App
            * An uploaded jar file can have the same Bundle-SymbolicName as a released App but its Bundle-Version should be different

            All the various combinations of what a developer can do are kind of complicated, and our current submit app feedback page does not do a great job of explaining what's happening when a developer submits an App jar. For example, we are telling the developer whether the uploaded jar file is a "new app," but there are several ways that an App can be new!

            Let's change the feedback page as follows:

            Instead of displaying the line: "Is the is a new App" and then showing either "Yes" or "No", let's instead display a different line: "App Summary" and give a simple sentence explaining what the developer is doing. If the developer reads this text, they will be able to decide whether to proceed with the next step of either canceling the submission or proceeding with submission.

            For the new design, please see this PowerPoint:

            (to be added)



            When developers upload an App, App Store must perform first-level automated review of the App to make sure it follows basic specifications. For example:

            * Jar file must contain OBR index file called "repository.xml" at the top level of the jar
            * Jar file MANIFEST must contain OSGi headers of Bundle-SymbolicName, Bundle-Version, and Bundle-Name (note that Bundle-Description is optional)
            * An uploaded jar file can have the same Bundle-SymbolicName and same Bundle-Version as a currently "pending" App, but not a released App
            * An uploaded jar file can have the same Bundle-SymbolicName as a released App but its Bundle-Version should be different

            All the various combinations of what a developer can do are kind of complicated, and our current submit app feedback page does not do a great job of explaining what's happening when a developer submits an App jar. For example, we are telling the developer whether the uploaded jar file is a "new app," but there are several ways that an App can be new!

            Let's change the feedback page as follows:

            Instead of displaying the line: "Is the is a new App" and then showing either "Yes" or "No", let's instead display a different line: "App Summary" and provide some text explaining what the developer is doing. If the developer reads this text, they will be able to decide whether to proceed with the next step of either canceling the submission or proceeding with submission.

            For the new design, please see this PowerPoint:

            https://www.dropbox.com/s/xe1v2jo17fg23th/SubmitApp-JarUpload.pptx?dl=0

            (This is the same PPT as for IGBF-1995, but with new slides added.)


            ann.loraine Ann Loraine made changes -
            Description When developers upload an App, App Store must perform first-level automated review of the App to make sure it follows basic specifications. For example:

            * Jar file must contain OBR index file called "repository.xml" at the top level of the jar
            * Jar file MANIFEST must contain OSGi headers of Bundle-SymbolicName, Bundle-Version, and Bundle-Name (note that Bundle-Description is optional)
            * An uploaded jar file can have the same Bundle-SymbolicName and same Bundle-Version as a currently "pending" App, but not a released App
            * An uploaded jar file can have the same Bundle-SymbolicName as a released App but its Bundle-Version should be different

            All the various combinations of what a developer can do are kind of complicated, and our current submit app feedback page does not do a great job of explaining what's happening when a developer submits an App jar. For example, we are telling the developer whether the uploaded jar file is a "new app," but there are several ways that an App can be new!

            Let's change the feedback page as follows:

            Instead of displaying the line: "Is the is a new App" and then showing either "Yes" or "No", let's instead display a different line: "App Summary" and provide some text explaining what the developer is doing. If the developer reads this text, they will be able to decide whether to proceed with the next step of either canceling the submission or proceeding with submission.

            For the new design, please see this PowerPoint:

            https://www.dropbox.com/s/xe1v2jo17fg23th/SubmitApp-JarUpload.pptx?dl=0

            (This is the same PPT as for IGBF-1995, but with new slides added.)


            When developers upload an App, App Store must perform first-level automated review of the App to make sure it follows basic specifications. For example:

            * Jar file must contain OBR index file called "repository.xml" at the top level of the jar
            * Jar file MANIFEST must contain OSGi headers of Bundle-SymbolicName, Bundle-Version, and Bundle-Name (note that Bundle-Description is optional)
            * An uploaded jar file can have the same Bundle-SymbolicName and same Bundle-Version as a currently "pending" App, but not a released App
            * An uploaded jar file can have the same Bundle-SymbolicName as a released App but its Bundle-Version should be different

            All the various combinations of what a developer can do are kind of complicated, and our current submit app feedback page does not do a great job of explaining what's happening when a developer submits an App jar. For example, we are telling the developer whether the uploaded jar file is a "new app," but there are several ways that an App can be new!

            Let's change the feedback page as follows:

            Instead of displaying the line: "Is the is a new App" and then showing either "Yes" or "No", let's instead display a different line: "App Summary" and provide some text explaining what we think the developer is doing. If the developer reads this text, they will be able to decide whether to proceed with the next step of either canceling the submission or proceeding with submission.

            For the new design, please see this PowerPoint:

            https://www.dropbox.com/s/xe1v2jo17fg23th/SubmitApp-JarUpload.pptx?dl=0

            (This is the same PPT as for IGBF-1995, but with new slides added.)


            ann.loraine Ann Loraine made changes -
            Resolution Unresolved [ 10101 ]
            Status To-Do [ 10305 ] In Progress [ 3 ]
            ann.loraine Ann Loraine made changes -
            Status In Progress [ 3 ] To-Do [ 10305 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status To-Do [ 10305 ] In Progress [ 3 ]
            ann.loraine Ann Loraine made changes -
            Status In Progress [ 3 ] To-Do [ 10305 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Assignee Riddhi Jagdish Patil [ rpatil14 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status To-Do [ 10305 ] In Progress [ 3 ]
            ann.loraine Ann Loraine made changes -
            Comment [ testing ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status In Progress [ 3 ] To-Do [ 10305 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Link This issue is blocked by IGBF-2050 [ IGBF-2050 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Link This issue is blocked by IGBF-2044 [ IGBF-2044 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status To-Do [ 10305 ] In Progress [ 3 ]
            ann.loraine Ann Loraine made changes -
            Status In Progress [ 3 ] To-Do [ 10305 ]
            ann.loraine Ann Loraine made changes -
            Sprint Fall 4 : 30 Sep to 11 Oct [ 75 ] Fall 4 : 30 Sep to 11 Oct, Fall 5 : 14 Oct to 25 Oct [ 75, 76 ]
            ann.loraine Ann Loraine made changes -
            Rank Ranked higher
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status To-Do [ 10305 ] In Progress [ 3 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status In Progress [ 3 ] To-Do [ 10305 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status To-Do [ 10305 ] In Progress [ 3 ]
            ann.loraine Ann Loraine made changes -
            Workflow Fall 2019 Workflow Update [ 20783 ] Revised Fall 2019 Workflow Update [ 21194 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Attachment something_wrong_page.png [ 14452 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Link This issue is blocked by IGBF-2081 [ IGBF-2081 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status In Progress [ 3 ] To-Do [ 10305 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status To-Do [ 10305 ] In Progress [ 3 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status In Progress [ 3 ] Needs 1st Level Review [ 10005 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Assignee Riddhi Jagdish Patil [ rpatil14 ]
            ann.loraine Ann Loraine made changes -
            Assignee Ann Loraine [ aloraine ]
            ann.loraine Ann Loraine made changes -
            Status Needs 1st Level Review [ 10005 ] First Level Review in Progress [ 10301 ]
            ann.loraine Ann Loraine made changes -
            Status First Level Review in Progress [ 10301 ] Ready for Pull Request [ 10304 ]
            ann.loraine Ann Loraine made changes -
            Assignee Ann Loraine [ aloraine ] Riddhi Jagdish Patil [ rpatil14 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status Ready for Pull Request [ 10304 ] Pull Request Submitted [ 10101 ]
            ann.loraine Ann Loraine made changes -
            Status Pull Request Submitted [ 10101 ] Reviewing Pull Request [ 10303 ]
            ann.loraine Ann Loraine made changes -
            Assignee Riddhi Jagdish Patil [ rpatil14 ] Ann Loraine [ aloraine ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Assignee Ann Loraine [ aloraine ]
            ann.loraine Ann Loraine made changes -
            Status Reviewing Pull Request [ 10303 ] Merged Needs Testing [ 10002 ]
            ann.loraine Ann Loraine made changes -
            Sprint Fall 4 : 30 Sep to 11 Oct, Fall 5 : 14 Oct to 25 Oct [ 75, 76 ] Fall 4 : 30 Sep to 11 Oct, Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov [ 75, 76, 77 ]
            ann.loraine Ann Loraine made changes -
            Rank Ranked higher
            shamika Shamika Gajanan Kulkarni (Inactive) made changes -
            Assignee Shamika Gajanan Kulkarni [ shamika ]
            shamika Shamika Gajanan Kulkarni (Inactive) made changes -
            Status Merged Needs Testing [ 10002 ] Post-merge Testing In Progress [ 10003 ]
            shamika Shamika Gajanan Kulkarni (Inactive) made changes -
            Assignee Shamika Gajanan Kulkarni [ shamika ] Riddhi Jagdish Patil [ rpatil14 ]
            shamika Shamika Gajanan Kulkarni (Inactive) made changes -
            Status Post-merge Testing In Progress [ 10003 ] To-Do [ 10305 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status To-Do [ 10305 ] In Progress [ 3 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Assignee Riddhi Jagdish Patil [ rpatil14 ] Shamika Gajanan Kulkarni [ shamika ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status In Progress [ 3 ] Needs 1st Level Review [ 10005 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status Needs 1st Level Review [ 10005 ] First Level Review in Progress [ 10301 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Assignee Shamika Gajanan Kulkarni [ shamika ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status First Level Review in Progress [ 10301 ] Needs 1st Level Review [ 10005 ]
            shamika Shamika Gajanan Kulkarni (Inactive) made changes -
            Assignee Shamika Gajanan Kulkarni [ shamika ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Assignee Shamika Gajanan Kulkarni [ shamika ]
            pbole Pawan Bole (Inactive) made changes -
            Assignee Sameer Shanbhag [ sameer ]
            pbole Pawan Bole (Inactive) made changes -
            Assignee Sameer Shanbhag [ sameer ] Ann Loraine [ aloraine ]
            pbole Pawan Bole (Inactive) made changes -
            Assignee Ann Loraine [ aloraine ]
            ann.loraine Ann Loraine made changes -
            Status Needs 1st Level Review [ 10005 ] First Level Review in Progress [ 10301 ]
            ann.loraine Ann Loraine made changes -
            Status First Level Review in Progress [ 10301 ] Ready for Pull Request [ 10304 ]
            ann.loraine Ann Loraine made changes -
            Assignee Riddhi Jagdish Patil [ rpatil14 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Status Ready for Pull Request [ 10304 ] Pull Request Submitted [ 10101 ]
            rpatil14 Riddhi Jagdish Patil (Inactive) made changes -
            Assignee Riddhi Jagdish Patil [ rpatil14 ]
            ann.loraine Ann Loraine made changes -
            Status Pull Request Submitted [ 10101 ] Reviewing Pull Request [ 10303 ]
            ann.loraine Ann Loraine made changes -
            Status Reviewing Pull Request [ 10303 ] Merged Needs Testing [ 10002 ]
            noor91zahara Noor Zahara (Inactive) made changes -
            Assignee Noor Zahara [ noor91zahara ]
            noor91zahara Noor Zahara (Inactive) made changes -
            Status Merged Needs Testing [ 10002 ] Post-merge Testing In Progress [ 10003 ]
            noor91zahara Noor Zahara (Inactive) made changes -
            Assignee Noor Zahara [ noor91zahara ] Riddhi Jagdish Patil [ rpatil14 ]
            noor91zahara Noor Zahara (Inactive) made changes -
            Resolution Done [ 10000 ]
            Status Post-merge Testing In Progress [ 10003 ] Closed [ 6 ]
            chirag24 Chirag Chandrahas Shetty (Inactive) made changes -
            Link This issue relates to IGBF-2766 [ IGBF-2766 ]

              People

              • Assignee:
                rpatil14 Riddhi Jagdish Patil (Inactive)
                Reporter:
                ann.loraine Ann Loraine
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: