Replies: 5 comments 4 replies
-
Looks good to me! This will clean some stuff like |
Beta Was this translation helpful? Give feedback.
-
I know it's a tricky one but maybe in the requirements we could add "The modal should play nicely with WebViews"? I detected some issues with Magic and the Android modal. But it's probably related to the keyboard handling |
Beta Was this translation helpful? Give feedback.
-
In the Modal View, what are you referring to when you say "use alert component"? |
Beta Was this translation helpful? Give feedback.
-
I think we'll need react navigation modal for screens where we use navigator to open the modal. |
Beta Was this translation helpful? Give feedback.
-
@gorhom now that we have the |
Beta Was this translation helpful? Give feedback.
-
Overview
With the scale of the ShowTime application the usage of modals had increased to more screens and views, which currently utilise
Modal
,ModalSheet
andReact Navigation Screen + Modal
.However, the current solution has issues:
these issues make it difficult to scale or maintain the current screen and the addition of new screens and views.
Requirements
// TBD
Suggested Solution
The goal of this initiative is to simplify the usage of modal views and screens in Showtime, abstracting all default implementation away from engineers and let them focus on the modal's content.
Modal View
Modal view is defined here in Figma. Where it has two look state for web and mobile platforms.
Modal view has 3 main components that should be usable in all platforms:
Requirements
onClose
,onDismiss
).Specifications
Modal Screen
Modal screen is defined here in Figma, where it renders differently for each platform.
Modal screen uses most of Modal view components but will differ in action handling, this component should be abstracted than screen root component.
Requirements
Specifications
Tasks
Beta Was this translation helpful? Give feedback.
All reactions