The experience
Invest by the dollar, not by the share.
Vestra is a retail investing app built on one idea: you decide how much money to put in, and the shares follow. The buy screen carries two linked fields — dollars and shares — and typing into either resolves the other live against the current price. $250 becomes 0.7791 shares while you watch, which is the whole fractional proposition delivered without a paragraph of explanation.
The demo is the client experience, whole: onboarding, sign-up, an email code, personal details with country of tax residency, funding, research over an interactive chart, order validation, a six-field confirmation under live Terms and Best Execution documents, payment authorisation, settlement, a portfolio with an allocation breakdown, and a transaction history with six filters. Thirty-four screens, including the failure results, the lockout state and the empty states a pitch deck skips.
It was ported from a real iOS retail-trading application, and it keeps that product's rules rather than inventing convenient ones. Its palette, type scale, button system and radius scale are the source's own design system — extended with the spacing, elevation, focus states and motion a web build needs and the source does not define, and with four colours darkened to stay legible as text on a light canvas. Whatever Itexus added on top is labelled as an addition everywhere it appears.
See one fractional order end to end, decision to settlement
Judge the flow the way your compliance lead will
Leave with a specification, not an impression
Who this is for
Everything except the client experience can be rented.
The regulated pieces of a fractional-investing product can be bought, rented or introduced. The surface a retail investor actually touches cannot, and it is the part the engineering estimate keeps growing around.
Licensed brokers adding fractional
You hold the licence, the custody relationship and the execution route. Fractional equities are a decision you have already made, or are one meeting from making, and the client app is the piece with no vendor to buy it from.
Neobanks and wealth apps
Investing is the next tab in a product that already has the customer, the balance and the funding rails. Before a roadmap commits to it, someone has to see what a credible dollar-first order flow actually looks like.
Brokers whose app predates fractional
You need a modernised flow to put in front of an investment committee before anyone funds a rebuild. This is that flow — clickable, in three versions, with the compliance-facing screens already drawn.
This positioning is a hypothesis drawn from the source product itself — its API surface, its single end-user role, its tax-residency fields — not a measured or client-confirmed segment. It is not aimed at self-directed investors, who are the end users rather than the buyer, and nothing here speaks to order books, margin or multi-leg orders. No market size, share, benchmark or competitor comparison appears anywhere on this page, because none of them has been verified.
The moment that sells it
Every trading app shows a confirmation list. This one shows an outcome.
Choose $250 of Northwind Grid Energy and tap Buy. Before any commitment, a preview opens: the allocation ring re-segments to what this order would leave you holding, the invested balance counts up, cash counts down by the same figure, the new position card rises in — and the portfolio total sits underneath it, marked unchanged. Five movements of 280 ms, started 40 ms apart, settling at about 420 ms and holding.
The recolouring is what reads across a room
A $250 order against a $20,666 portfolio moves allocation by 1.2 points — roughly four degrees of arc, which no amount of animation makes visible from the back of a meeting room. So five wedges recede to 28% opacity while the new holding keeps full chroma, and the ring's centre counts to 26.4% of portfolio. That, plus two counters rolling, is what the eye catches.
Conservation is shown, not asserted
Invested $17,849.98, up $250. Cash $2,816.80, down $250. Portfolio total $20,666.78, unchanged — on one surface, in the same moment. Nobody has to take it on trust that the money did not come from nowhere.
It is labelled as ours, on the sheet itself
The panel carries a Proposed by Itexus badge and the words Not in the source product, and the guided tip says the same thing in a full sentence. Nothing about the order changes: the same six-field confirmation, under the same Terms and Best Execution links, still gates it.
Under prefers-reduced-motion the same values change without transition and the flow still completes. And one thing worth saying out loud: the first build of this step counted the portfolio total in the largest type on the screen — a figure that is identical before and after, so the headline number counted from itself to itself. Two design reviewers measured it independently and failed the verdict on it. The headline now counts the invested balance, which genuinely rises, and the unchanged total is stated underneath, where it belongs.
Suggested walkthrough
A guided path through the strongest moments.
Seven minutes for the main story, ten to twelve with a supporting flow. There is nothing to sign up for and no credentials to look up — the demo opens as a funded demo client. The full account-opening flow, email code and tax-residency fields included, is one click away under About this demo, and it is the first place a compliance-minded buyer should go.
Find something
Tap Search assets, type Northwind, open the instrument, and switch the chart period once.
A price header, an interactive chart over 1D, 5D, 1M, 6M, 1Y, YTD and ALL, eight key statistics, an About section and news. The redraw is instant, which tells you the chart is drawn rather than pasted in.Choose an amount
Tap Buy, then type 250 — or use one of the five quick amounts the source product defines.
The share quantity resolves live against the price: 0.7791 shares at $320.88. Type into the share field instead and the dollars follow. Ask for fifty cents' worth and the minimum-order rule stops you.See the impact
Tap Buy again, and read the panel that opens before you have agreed to anything.
The moment the demo exists for. The ring re-segments, invested counts up, cash counts down by the same figure, and the portfolio total underneath is marked unchanged. It carries a Proposed by Itexus badge, because it is not in the source product.Confirm and authorise
Continue to confirmation, read the six fields, then Submit.
Amount, price, estimated shares, fees, traded value and time in force, under Terms and Best Execution documents that open for real. A six-digit code arrives in a panel that is visibly part of the demo, and one tap fills it. Get it wrong three times and the attempt locks, exactly as in the source.See it land
Okay, then open Portfolio.
The position sits in My Stocks with its average entry price. Cash is down $250.00, investments are up $250.00, and the portfolio total has not moved — the balance identity holds after every operation, which is a test rather than a coincidence.Beyond the happy path
Scenarios: the situations the walkthrough does not reach.
The demo carries a Scenarios control in its top bar. It is a demo instrument rather than part of the product: each entry loads a different starting state — an edge case, a failure, a rule firing — and the screens recompute from it. The guided path shows the product working. The scenarios show what it does when the situation is not the ideal one.
One button, at any point in the demo.
Pick a scenario and the demo re-seeds itself and opens on the screen where that situation shows. Nothing has to be set up beforehand, and you can go back to the guided path whenever you want.
The states a product actually lives in
A limit that is used up, a figure that has gone stale, an approval that comes back as a question. These are the cases that decide whether a product survives contact with real users — and here each one is a state you can open, not a sentence you have to take on trust.
A rule you can trigger, then watch
A scenario sets up one condition and lets the system react to it. What appears on screen is computed by the same logic that runs the happy path, so the numbers, the blocks and the explanations behave as they do in the rest of the demo.
Your “what happens when…”, on the spot
The questions that decide a project are usually failure questions. If yours has a scenario, play it during the walkthrough and judge the answer on screen instead of waiting for a follow-up e-mail.
Scenarios are a demo control and never appear inside the product itself. Every state they load is built from the same fictional data, and Reset returns the demo to its clean starting seed.
Why this is not a mockup
Three rules that came out of a codebase, not a design brief.
Anyone can draw a buy screen. These three behaviours exist because they were read out of a real implementation, and each is the kind of thing a compliance lead asks about in the first ten minutes.
Validation is its own call, and it has to answer first
In the source, an order is validated by a separate request that returns a request id, the amount, the traded value and the fees — and the buy call takes that id. The confirmation screen is not reachable until it comes back. That two-phase order is what makes the fee and traded-value disclosure honest, and any backend put behind this client has to keep it.
Six fields on the confirmation, not a summary line
Amount, price, estimated shares, fees, traded value, time in force — under a Terms of Service and a Best Execution Policy that open as real documents inside the demo, with the indicative-price and capital-at-risk notice beside them. The set and its wording are the source product's, not a designer's shorthand.
The rules fire when you push at them
Minimum order one dollar. Nothing above available cash. Nothing sold beyond the position you hold. Portfolio equals investments plus cash after every operation. Push at any of them and the demo stops you, because each one is enforced in the runtime and covered by its own test.
Capability map
Clear about what you're experiencing.
Works in this demo
Implemented and clickable, on fictional data, in all three display versions.
- Search across 27 instruments, with a designed empty state
- Instrument detail: interactive chart over seven periods, eight key statistics, About and news
- Two-way dollar ⇄ share conversion at the live price, in either direction
- Order validation before confirmation, enforcing the source product's own rules
- The six-field order confirmation, with working Terms and Best Execution documents
- Buy, sell by shares, sell by amount and close-position, each with its own confirmation
- Portfolio with separate portfolio, investments and cash balances, positions with average entry price, and an allocation breakdown
- Funding and withdrawal, with confirmation and result screens including the failure result
- Transaction history with six filters, and a detail view with reference number and status
- Collections: create, add instruments, grid ⇄ list, remove, delete
- Account opening: onboarding, sign-up, email code, personal details, tax residency and tax number
- Light and dark themes, three display versions, guided mode, one-click session reset
Simulated here
Behaves like the real thing and reaches nothing. No order, no payment, no message, no identity check.
- Orders — no order reaches any venue; the position is added to your local session
- Payments — top-up and withdrawal move a number, not money
- The verification code — drawn in an in-demo panel labelled nothing is really sent; no email or SMS is dispatched
- Identity checks — no KYC provider is contacted; the tax fields are collected and then discarded
- Prices and instruments — generated deterministically; the Meridian Exchange does not exist
Ready to integrate
Candidates for a production build. Nothing here is connected, and nothing here is selected.
- Market and reference data for prices, bars, fundamentals and news
- An execution venue or introducing broker for order routing, with fractional aggregation
- A custodian for positions and corporate actions
- An identity and tax-residency verification provider
- Payment rails for funding and withdrawal
- A document service for statements, contract notes and tax reporting
- A notification service for the codes the demo draws itself
Completed and proposed
What came from the source, and what did not.
One part of this demo is a proposal and two were completed rather than carried over. The difference is marked here and on screen, because it is what tells you which work was the source product's and which was ours.
The order-impact preview
Proposed by ItexusIt does not exist in the source product. It carries that badge on the sheet, its guided tip says so in words, and in the claims register behind this page it is recorded as possible — never as source-backed. Calling it a feature of that product is prohibited wording here, not a matter of taste.
In-demo delivery of the verification code
Completed for the demoThe source product sends a real email. The demo emulates the channel: the code is drawn in a panel tagged nothing is really sent, deterministic from the session, fillable in one tap and still typeable by hand. The behaviour behind it — six digits, a resend timer, a lockout after three wrong attempts — is the source's.
Collection cover art
Completed for the demoThe source opens the device photo picker, and its own API has no upload endpoint behind it. The demo generates a cover instead, and says so on the create screen rather than in a footnote.
Guided mode, version selector, About this demo, reset session
Demo shellScaffolding for showing the product, not claims about it. None of it exists in the source product and none of it is offered as product functionality.
None of it moves a regulated step. The order still validates before the confirmation is reachable, the six fields still gate it, payment still needs its code, and the account still asks for country of tax residency and a tax number before trading.
However you open it
Three display versions of the same demo.
One build, one route, three versions, switchable from the header in the middle of a flow. The route and a pending order both survive the switch, so a buyer can start on a shared screen and finish on the phone in their hand without losing their place.
Web · desktop
A multi-column layout with a persistent sidebar and table density, none of which exists in the source product: the tokens are the source's, the desktop layer is new. Above 1180px the impact sheet opens to 880px with the ring and the numbers side by side.
Web · mobile
One column at phone width, a four-item tab bar, full-width fields and targets sized for a thumb. Same session, same seed, same rules, same wow moment — stacked rather than side by side.
Native app
An emulation of the iOS product the screens were ported from, framed as a phone on a wide viewport and unframed on a narrow one. Labelled as an emulation, because it is a web build and not a native binary.
Narration built in
Guided mode
On by default. A dismissible tip on each screen says what the screen is, what you can do here and where to go next — naming the product's rules outright, including the one that says the impact preview is our proposal rather than the source product's feature. It is drawn on the demo's own surface, never inside the app's layout: beside the phone in the native version, in the gutter when the gutter is genuinely wide enough, docked above the tab bar when it is not, and never over the disclosure badge or the primary action. The whole flow completes with it switched off.
From demo to production
What each simulated part is standing in for.
The demo is a client experience over a deterministic in-browser adapter. Here is what each simulated part stands in for — read from the source product's own API surface rather than proposed from scratch. Nothing below is implemented, and none of it is a readiness statement.
The part worth raising before you do: most venues do not trade fractions. A production build aggregates fractional client orders into whole-share orders, executes those, and allocates the fractions back from the firm's own position — which means an inventory account, an allocation ledger, and a stated policy for when aggregation cannot fill. It is the single largest piece of work sitting behind the screen this demo makes look simple, and it belongs in the first conversation rather than the third.
Built to adapt
The regulated pieces can be rented. The experience cannot.
The source is one product for one market. What carries into another licence, another jurisdiction or another app is the flow underneath it — and the discipline about which link in the chain belongs to whom.
Depth, not a slide
Thirty-four screens: failure results, a lockout state, empty states, tax residency, a filterable transaction history with reference numbers. The parts a pitch skips are the parts compliance asks about first.
The rules came from a real app
Minimum order, validation before confirmation, the six confirmation fields, the balance identity. Each is traceable to the source implementation and covered by a test, rather than invented for a demo.
One idea they can ask for
The order-impact preview is a concrete proposal a product owner can point at — and we will say plainly, unprompted, that it is ours rather than the source product's.
Three versions from one build
Desktop, mobile web and a native-app emulation, switchable live in the same session without losing the route or a pending order.
Discuss with Itexus
Decisions to shape for your product
- Which of the three versions matches where your users actually are?
- Does fractional aggregation happen at your broker today, or would it need building?
- How much of the account-opening flow is already covered by your KYC vendor?
- Would the impact preview sit before or after best-execution disclosure in your jurisdiction? It could be built without changing order semantics, fees, disclosure or suitability logic — none of which has been implemented in production anywhere.
- What would you have to add to this flow before compliance would sign it off?
- Where does execution happen today, and who has to say yes besides you?
Before you begin
Demo boundaries and data policy.
Known limitations
- One market, one currency and one order type: USD, a single fictional exchange, market orders with day validity. No limit or stop orders, no recurring investment, no options and no margin.
- No dividends and no corporate actions, and no partial fill or rejection. The source product models a single executed outcome, so the demo does too — production would need screens neither of them has.
- One role. The source product has a single end-user role, so there is no adviser, admin or back-office view to show.
- The demo clock is pinned to one moment, so prices do not move while you watch and “2 hours ago” always means the same thing. That is deliberate: it keeps every screenshot permanently true.
- Session state lives in one browser tab. Two tabs are two independent sessions, closing the tab ends the demo, and Reset returns to the seeded scenario.
- English only, behind a language selector with exactly one option — as the source product's has.
- Not ported: biometric unlock, keychain storage and refresh-token rotation, push notifications, the device photo picker, and a support hand-off that would navigate out of the demo into a real external channel.
- Accessibility was checked by automation only — axe-core across eight screens in three versions and two themes, with no critical or serious violations. That is a sample under automation: not an audit, not a conformance statement, and no testing with assistive technology or with disabled users was performed.
- Verified in Chromium and WebKit, both pinned. Firefox was not tested.
Data and safety
- The data in this demo is fictional and generated.
- No action taken in this demo is performed in any production system.
- Do not enter real personal, payment or document data.
- Simulated KYC, payment, brokerage, AI and other providers are not connected to production.
- Functionality that was completed or proposed by Itexus is marked as such and is not an existing feature of the source product.
- Nothing in this demo is investment advice. The value of investments can fall as well as rise.
- Every instrument, price, person, transaction and document is invented, and the exchange is fictional so that nothing on screen can be mistaken for a real listing.
- After it loads, the demo makes no request of its own: no backend, no API, no analytics in the build and no cookies — its own security policy refuses a fetch outright. The hosting platform injects an analytics tag at the edge, and that policy blocks it before anything is fetched, so nothing about your visit is reported. Verified on the live URL, not only locally.
Provenance
- Source product
- A real iOS retail-trading application, read at its development head of 18 December 2025. Every statement about the source describes it at that point, and no source code was ever executed — the repository was read, never run.
- Positioning
- A hypothesis derived from the source product itself, not a measured or client-confirmed segment. No market size, share, competitor comparison or conversion figure appears on this page, because none has been verified.
- Conformance
- No audit, assessment or certification against any standard was performed. The demo makes no conformance statement about any regulation, and the accessibility result above is an automated sample rather than a conformance claim.
- Verification
- 82 of 82 runtime tests pass in Chromium and WebKit, and 23 of 23 checks pass against the deployed URL. Two independent design reviews over three rounds returned a combined verdict of pass.
- Content version
- 1.0.0, verified against the deployed demo on 30 July 2026. Every claim on this page is registered against evidence; the ones that could not be backed are not here.