Industry
We build websites and mobile apps for startups building products in payments, wallets, personal finance, investment or insurance, and for companies offering financial services. In this field, before trusting you with their money or personal data, users want to see who provides the service, what they will pay and where their data is kept. We build the site and the app to answer those three questions plainly.
01Needs
With a financial product, the decision rests on trust, and trust is built in the details. Once visitors understand what the product does, they look at the following: which company provides the service, what its registered name and address are, how much is charged for which transaction, what limits apply, where money and data are kept, and who to contact if something goes wrong. This information should not sit behind a small link at the bottom of the site, but on its own pages in plain language.
On the app side, the first impression is the sign-up flow. If identity verification, phone confirmation and password steps do not tell users why they are being asked for, the flow is abandoned halfway. If identity verification is required, that step connects to the verification provider you have chosen and contracted with; the choice and the responsibility are yours.
Behind the scenes, an admin panel is almost always needed: a screen where the support team can find a user, see transactions, and where a record is kept of who accessed what. The roles and permissions of this panel should be designed from the start, together with the app’s screens.
02What we build
03Services
In a financial app, flows are written before screens are designed: sign-up, verification, login, transaction confirmation, account deletion. Security decisions such as biometric login, session length and device changes go into the scope document; developer accounts and source code are set up in your company’s name.
On a fintech site the fee table, the security page and the company information page carry as much weight as the product page. We define the content fields one by one so that texts approved by your legal team can go onto the page unchanged.
The admin panel, internal operations screens and integration with the bank or payment institution you work with fall under this heading. Who can see what in the panel, and a record of every action taken, are designed from the start.
Finance searches are mostly phrased as questions: how a product works, what it costs, how to open or close it. We plan guide pages that answer these questions; content that could be read as investment advice is left for your review before publishing.
Financial services ads are subject to additional platform rules. We write ad copy according to these rules and the fee information on your site, and track app installs, completed sign-ups and application forms as separate conversions.
04Search and ads
05Things to check
06Example
A personal budgeting app for tracking spending and assets, live on the App Store and Google Play.
Mobile app
07FAQ
Development can technically start, but which features can be offered under which permission directly affects the product’s scope. So we suggest writing the scope together with your compliance adviser’s view and keeping the release date tied to the licensing process.
No. Identity verification, payment or banking infrastructure comes from providers you have contracted with. We connect the app and the panel to those providers’ APIs; choosing and contracting the provider is up to you.
That is a decision to make before the server and database are set up, and it should be weighed together with your legal obligations. We write the options and the consequences of each into the scope document; you make the decision together with your adviser.
It depends on where and how often users will use the product. For products used daily that need notifications and biometric login, a mobile app comes first; for products serving business users at a desktop, a web app. We separate together in the scope which one is essential in the first release.
Apple and Google require apps that let users create an account to offer an account deletion request inside the app. If you have records you are legally required to keep, decide with your adviser which data is deleted and which is retained; we build the flow and the text shown to users accordingly.
Rufy Studio
Tell us what you are building, who your target users are, where your licensing process stands and which providers you work with; we will suggest a scope based on that.