Problem

Currently, in status-im.contexts.wallet.send.routes.view we use the routes array returned from status-go endpoint to render cell items of Network Bridge and Network Links components. This approach won't work for some cases, for example, when the sender sends from three networks and the receiver received in two (one-to-many), because we are using a FlatList and the approach is linear (we always show a Network Bridge in the From and To columns for each item [(one-to-one)]). We may want to show a connection between one to multiple networks, and for that we need to refactor the logic and probably a list is not what we want for this case.

Example:

Acceptance Criteria

• Do not break current UI.
• Extend the possibilities to allow all the cases like the one on the Figma designs (one-to-many network connections).
• If possible, create a preview screen to test different cases, because we currently depend on getSuggestedRoutes endpoint response for rendering these components and the connections.
• Polish and refactor code in status-im.contexts.wallet.send.routes.view file which is complicated and with this new approach without FlatList should be cleaner and easier to understand.