1500+ ready React Native mobile app screens

Affiliates
App sets

Rail

12 screens · Payments and transfers

Payouts that tell you when the money actually lands

Twelve screens of a business payments app built on the gap every other one hides, which is the distance between a payment being sent and the money being spendable, with every settlement date, cut off time, fee, conversion and available balance on every screen derived from the rail it travels on rather than asserted as a single sent status.

PRO

The design system and all 12 screens in one prompt. Each screen is also on its own page, free, if you only want one.

Design system

One file, shipped with the set. Every screen declares these values inline so it can be lifted out on its own, and the build refuses a screen that paints a colour this file does not name.

Colours

palette
ground
#FFFFFF
field
#F4F4F5
sunken
#E9E9EA
line
#E4E4E5
ink
#121212
inkMuted
#6B6B6B
inkFaint
#9B9B9B
accent
#1B51D6
onAccent
#FFFFFF
data
arrived
#12B76A
inflight
#3E7BFA
failed
#C4362C
neutral
#C9C9C9

Scales

radius
tile8
card12
sheet20
pill999
space
gutter20
gap12
row16
section30
text
display34
title20
body15
label12
micro10
Typeface
Inter, 5 weights

The flow

In the order somebody meets them. This is the app's own sequence, not a list of categories.

The money

4

What is actually available as against what merely exists. Three settlement states, a ledger that separates them, and the detail behind one payment.

Paying out

4

Choosing a rail is choosing a trade between speed, cost and cut off. Four screens that put that trade in front of the person making it.

Getting paid

4

The other direction. Invoices with real ageing, the customers behind them, what the month actually collected, and the account itself.

Rail, a 12 screen app | Clevens