Problems with existing mobile components

[lindapaiste]

I'm making this issue to document some of the problems with the existing MobileIDEView (and other mobile components) and keep track of them as I fix them. There are a lot of features that haven't been implemented, but I'm focusing more on bugs and mistakes.

Note that none of the mobile UI is available to end users at the moment due to the MOBILE_ENABLED flag, which is false in production.

• 1. Theme not applied to Preferences:
  Fixed by Fix problems in MobileIDEView (#2184) #2185

• 2. 404 Not Found error when accessing /preferences directly:
  These URLs need to be added to the server in addition to the client. Which is simple enough, but also annoying and feels fragile.

• 3. App crashes when selecting Theme due to invalid value "Dark" instead of "dark".
  This gets saved to the user's preferences in the API and cannot be fixed by the user.
  Fixed by Fix problems in MobileIDEView (#2184) #2185

• 4. Prop-types warnings:
  Fixed by Fix problems in MobileIDEView (#2184) #2185

• 5. Props passed to PreviewFrame which don't do anything, because that component only accepts one prop (fullView):
  Fixed by Fix problems in MobileIDEView (#2184) #2185

• 6. Preview doesn't do anything, due to these postMessage errors:
  I have not figured out why this works on the desktop version but doesn't work here.
  

[dewanshDT]

hey @lindapaiste I'm already working on these issues on this branch dewansh-mobile, but these issues are not well documented

[lindapaiste]

hey @lindapaiste I'm already working on these issues on this branch dewansh-mobile, but these issues are not well documented

ah cool. I see you found a use for the FloatingNav, which I deleted in my PR because it's not used anywhere. whoops.

I managed to fix most of the issues in my list but not all of them. I'm mostly trying to get it to a "clean slate" point where you and me and anyone else can work on finishing the mobile UI [redacted] from a better starting point.

[dewanshDT]

yeah, that would be great!

[raclim]

@lindapaiste Thanks for your work on this so far!

We encourage contributions from all types of learners with varying backgrounds and levels of knowledge, so some of the code in this repository might not reflect as much technical experience as others. I feel that referring to someone else's prior work like that might be discouraging, and kindly suggest aiming towards language that's mindful of everyone's contribution journeys!

[lindapaiste]

Closing as stale since we are no longer using these particular components.