Tracking ant-design-mobile-rn 5.0 #1187
Description
🌄 Overview:
This issue is to track development on ant-design-mobile-rn 5.0 : the revitilization update 🏆 and has come out of a previous discussion here.
The goal of this project is to revitalize ant-design-mobile-rn with the vision of being a 1:1 component library to ant-design.
ant-design offers world class enterprise components for React.js. The react-native community needs ant-design components to bring enterprise-level components to mobile platforms, as not many libraries offer enterprise-level components for react-native.
Support and development on ant-design-mobile-rn has died out slowly since this library has been maintained by individual developers, but none-the-less we stand on the shoulders of giants and strictly follow the ant-design design language.
This project will detail all of the ant-design components and APIs that we have left to make ant-design-mobile-rn up-to-date with ant-design.
This will be a long journey, but it must be done.
🎯 Goals:
-
Update
ant-design-mobile-rnto include all (or most) of the components inant-design. -
Add some new mobile-only components to the library -- if possible
-
Completely revamp the docs to more accurately reflect categorization and documentation of new and old components.
📑 The details:
I have performed an initial grouping, comparing the existing ant-design-mobile-rn components that match up with ant-design.
Most of the unassigned components (i.e., components that don't have a 1:1 matchup to ant-design are mobile-only, or components that only make sense on mobile devices (for example... the native pickers).
| Unassigned components from ant-design-mobile-rn |
|---|
| ActionSheet |
| SwipeAction |
| SearchBar |
| NoticeBar |
| PickerView |
| Picker |
| Toast |
| SegmentedControl |
| Flex |
| WingBlank |
| WhiteSpace |
Below is the main progress table.
The complete column shows if the Component or group of components is complete.
The ant-design components and ant-design-mobile-rn components (assigned) columns link to the respective components in each library.
The Issue Link column is a link to the issue that tracks on a deeper level discussion and development of the component. An issue can be created for each component or component group as we get to it.
I will work on a PR overhauling the docs, to properly categorize components as ant-design and coordinate with progress on the component-level to test and update component APIs in the docs.
I know @1uokun has started on component dev for the following components see here, maybe we can start with form ? Let me know.
To keep this thread clear, only comment about updates to the master list. For discussion on development of a new component or a re-factor of an existing component, create the issue for that discussion and dev...next, comment here so I can update the master list with the link to the issue or feature.