Overhaul the UI to use webviews

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
react, react-native, typescript
Domain
frontend, mobile

Research direction

No files, tests, or entry points are identified. Start by locating the current React Native UI and the manager UI responsible for rendering the explorer and addons, then assess the web UI dependencies and polyfill constraints described here. Done would require an agreed and implemented webview-based rendering approach with its scope and validation defined.

Written by the indexing model from the issue text.

Description

help wanted

The RN UI is currently build all in RN. This makes it very time-consuming.
We're for the most part unable to re-use the web-UI because it depends on loads of dependencies that are not suitable for RN. There's also the polyfill issue that's not easy to resolve.

If we want to make this easier we should consider this:

Using web-views with the manager's UI in it for rendering the explorer & addons.

Screenshot 2020-01-27 at 13 05 52

Dominant language
TypeScript
Stars
1.3k
Forks
184
Avg merge
21m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from storybookjs/react-native

All issues in storybookjs/react-native

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.