Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • Review the latest Roadmap + Quick Discovery efforts

  • First product mobile sub-group meeting

\uD83D\uDDE3 Discussion topics

Time

Item

Notes

Roadmap Recap / Review

Missing:

  • Internationalization / RTL support - not currently in the mobile roadmap document

Learning Academy Selection

  • Quick Discovery: Learning Academy Selection

    • Canvas / Moodle / Open LMS - applications do this today, but what are the details of this workflow?

      • Moodle:

        • APIs for Moodle are open / available, could use this for discovery / review

        • Most LMS data (enrollments, students, content etc possible via APIs)

      • Canvas

        • They don't recommend using the open source platform

    • Might this be helpful also for multi-LMS platform type instances as well? (for platform selection step / upfront)

  • Options for Open edX instances adopting mobile:

    • No Mobile - sad, but the current default.

    • Dedicated App: Separate white label build of the mobile application, expensive option for many.

    • General Open edX / Provider specific app that can contains hundreds or more learning academy options

  • What is the priority / impact of this functionality?

    • How many open edx sites would raise their hand to use the Open edx or a provider build application? Can we get that information early?

    • How many people would instead opt for custom built apps if the Tutor plugin / build improvements help lower the cost dramatically for app builds.

    • Is the multiple learning site selection functionality valuable / essential? what headaches do we take on if we do the switching behavior.

  • For dynamic themes / theme loading what additional tech discovery should be done here?

    • Building the easily themable custom app build would help us understand what areas / elements are themable.


Offline Content Modes

  • Stateless + Stateful Content Blocks

    • many challenges with syncing state

Prioritization / Usage

  • How can we determine which features are essential in the existing applications and how can that help prioritization.

  • Having this wold let us add prioritization to feature + capability matrix + roadmap

✅ Action items

  •  

⤴ Decisions

  • No labels