Uploaded image for project: 'SimplyE 2.0'
  1. SimplyE 2.0
  2. SIMPLY-2287

Single Activity UI Rebuild

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • Android
    • None
    • S24 November 13 - November 27, S25 November 27 - December 11, S20 SIMPLY Sep 17 - Oct 1, S21 SIMPLY Oct 1 - Oct 15, S22 SIMPLY Oct 16 - Oct 30, S23 SIMPLY Oct 30 - Nov 13, SIMPLY S2 January 7- 21, SIMPLY S3 January 21 - Feb 4, SIMPLY S4 February 4 - 18, SIMPLY S5 Feb 18 - March 3, SIMPLY S6 March 3 - March 17, SIMPLY S7 March 17 - March 31, SIMPLY S8 March 31 - April 14, SIMPLY S9 April 14 - 28, SIMPLY S10 April 28 - May 12, SIMPLY S11 May 12 - May 26, SIMPLY S12 May 26 - June 9, SIMPLY S13 June 9 - June 23, SIMPLY S14 June 23 - July 7, SIMPLY S15 July 7 - July 21, SIMPLY S16 July 21 - August 4, SIMPLY S17 August 4 - 18, SIMPLY S18 August 18 - Sep 1, SIMPLY S19 September 1 - 15

      1) The screens listed below comprise the app, and need to be converted to Fragments from Activities:
       
      Feed view
      Feed with lanes
      Feed without lanes (grid view with cells)
       
      Book detail view
       
      Error page
       
      Settings screen

      • Accounts list
      • Account details page
      • Documentation screens (faq, license, etc)
      • Developer settings / version
         
        Profile screen
      • Profile creation
      • Profile selection
         
        Splash screen
      • Loading screen
      • Migration screen
         
        Card creator (NYPL SimplyE only)
         
        EPUB reader*
        Audio book reader*
        PDF reader*
        *The EPUB reader, the Audio book reader, and the PDF reader will remain
        as activities for now (so it's a four Activity app instead of strictly
        single-Activity!).
         
        2) The existing catalog views (such as the lanes and book cells) will be
        replaced with modern equivalents using the Android Paging library and
        rxjava2 (instead of our home-grown Observable class).
         
        3) We will separate each of the screens into their own modules to eliminate strong coupling between the existing pieces of the app UI.
         
        We will then create a new main Activity that hosts a navigation controller
        and that handles moving between screens (fragments) in the app. We'll
        replace the awful Navigation Drawer with a tabbed view as in iOS.
         
        The main activity will take a parameter that allows for directing the
        user to a specific point in the app. This is useful for, for example,
        implementing notifications that take the user directly to their book
        shelf instead of just dumping them into the default catalog.
         
        Finally, we need to provide a generic bare-bones profile screen (just
        so that there's a default) but implement an API to allow specific
        frontends to override these screens with their own versions. The LFA's
        current app selections have extremely application-specific fields on
        the profile screen such as "Are you a student at one of the LFA's pilot
        schools?".
         

       

        1. SingleActivity_Conversation.PNG
          SingleActivity_Conversation.PNG
          85 kB
        1.
        		 SA: Implement book detail fragment Sub-task Done Mark Raynsford
        2.
        		 SA: Implement a Settings screen fragment Sub-task Done Joseph Dalton
        3.
        		 SA: Implement profile screen fragments Sub-task Done Joseph Dalton
        4.
        		 SA: Adjust splash screen fragments Sub-task Done Joseph Dalton
        5.
        		 SA: Card creator Sub-task Done Malcolm Woods (Inactive)
        6.
        		 SA: Implement a service directory to avoid fragment coupling Sub-task Done Mark Raynsford
        7.
        		 SA: Implement a navigation controller and tabbed view Sub-task Done Joseph Dalton
        8.
        		 SA: Provide an API for direct navigation to places in the app Sub-task Done Joseph Dalton
        9.
        		 SA: Replace Observable with rxjava2 Sub-task Done Joseph Dalton
        10.
        		 SA: Implement an error page fragment Sub-task Done Joseph Dalton
        11.
        		 SA: Implement a feed with groups fragment Sub-task Done Joseph Dalton
        12.
        		 SA: Implement a feed without groups fragment Sub-task Done Mark Raynsford

            markraynsford Mark Raynsford
            andrewshelton Andrew Shelton
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: