There is a quiet assumption built into a lot of financial and legal software: that the user is sitting at a laptop, with a stable connection, a large screen, and a device that is theirs alone. For a great many families, especially across India, the Middle East, and much of the world BlockWill serves, none of that is true. The family computer is a phone. Often it is one phone, shared. It is the device the whole household uses for banking, messaging, identity, and now, increasingly, for the things estate planning is supposed to protect.

If a product only feels right on a laptop, it quietly excludes those families. Estate planning is exactly the domain where that exclusion is least acceptable, because the people who most need a clear path for their assets to reach their family are not a narrow, desktop-using slice of the population. So we design BlockWill mobile-first, and not in the shallow sense of a responsive layout. Designing for one-phone families changes real decisions.

The phone is not a small laptop

Mobile-first is often treated as a layout exercise: take the desktop design and reflow it for a narrow screen. That misses the point. The phone is a fundamentally different context. It is used in short bursts, often interrupted, frequently on imperfect connectivity, sometimes one-handed, sometimes by someone whose eyes are tired or whose first language is not the interface language.

Designing for that means rethinking flows, not just resizing them. Long forms that are tolerable on a desktop become punishing on a phone. So we break estate setup into small, resumable steps that each complete a meaningful unit and save immediately, so a person interrupted after two minutes loses nothing and can pick up later exactly where they were.

Designing for a shared device

The one-phone reality introduces a constraint most software ignores: the device is shared. The person setting up a will may be handing the same phone to a child for homework an hour later. That changes how we think about privacy and sessions.

We lean on hardware-backed passkeys precisely because they fit this world. A passkey (Face ID, a fingerprint, or a device PIN) ties access to a biometric or secret that the phone's owner controls, rather than a password that could be seen, reused, or left logged in. Sensitive views require re-authentication rather than assuming whoever holds the phone is the account owner. We avoid leaving readable sensitive content sitting in a session that the next person to pick up the phone could stumble into. On a shared device, an aggressive logout and a quick passkey re-check are features, not friction.

Connectivity you cannot assume

A one-phone family is also more likely to be on intermittent or metered data. A design that assumes a fat, always-on pipe will fail them at the worst moments. So we keep payloads lean, we make the critical paths work with minimal round trips, and we design for graceful recovery when a connection drops mid-step rather than losing the user's work.

Because BlockWill encrypts on the device before upload, the heavy cryptographic work happens locally, which actually suits this context: the network is only ever moving compact encrypted blobs, not large plaintext transfers, and the security model does not depend on a perfect connection.

Passkeys on phones, done carefully

Passkeys are a natural fit for mobile, but they raise a real question for estate planning: what happens if the single phone is lost, broken, or replaced? For a one-phone family, losing the device cannot mean losing access to the estate.

This is why we treat multiple key registration as essential guidance rather than an advanced option, and why we design the prompts to encourage at least one backup path, whether a second trusted device, a backup contact, or a recovery method established at setup. The mobile-first design has to actively steer a one-phone household toward redundancy, because the default of a single device is exactly the fragile case we need to protect against.

Language, literacy, and clarity

Designing for a broad mobile audience also means writing for it. Short sentences. Plain words. No jargon where a common word will do. Clear labels over clever ones. Visual steps that make sense even when read quickly on a small screen. This benefits everyone, but it is decisive for users who are reading in a second language or who are not steeped in financial terminology.

The test we apply is whether a capable adult who has never used a product like this could complete the essential task on a phone, on uneven connectivity, without help. If they cannot, the design is not done.

Why this is a category decision, not a styling one

The choice to be genuinely mobile-first is upstream of almost everything: how we chunk flows, how we handle sessions, how we treat connectivity, how we guide people toward recovery, how we write. It reflects a belief about who estate infrastructure is for. If digital inheritance is going to be infrastructure rather than a luxury product, it has to work, comfortably and safely, for the family whose entire digital life runs through a single shared phone. That is not an edge case to accommodate. For much of the world, it is the center.

Frequently Asked Questions

What does mobile-first estate planning mean?

It means designing the estate planning experience for a phone as the primary device from the start, not adapting a desktop design afterward. It affects how flows are chunked, how sessions and privacy work on shared devices, and how the product handles uneven connectivity.

What is a one-phone family?

A household where a single shared smartphone is the main or only computing device for the whole family. This is common across much of the world and shapes how privacy, sessions, and recovery need to be designed.

How does BlockWill handle privacy on a shared phone?

By relying on hardware-backed passkeys tied to the owner's biometric or device secret, requiring re-authentication for sensitive views, and avoiding leaving readable sensitive content in a session that another household member could open.

What happens if the only phone is lost or broken?

BlockWill treats registering more than one access path as essential, encouraging a backup device, a backup contact, or a recovery method set up at the start, so a lost phone does not mean lost access to the estate.

Why does connectivity matter for estate planning design?

Users on intermittent or metered data need flows that work with minimal round trips and recover gracefully when a connection drops. Because BlockWill encrypts on the device, the network only moves compact encrypted data, which suits imperfect connections.

Does mobile-first design make the product less secure?

No. The encryption and verification are the same. Mobile-first design mainly changes how flows are structured, how sessions behave on shared devices, and how recovery is encouraged, all of which can strengthen real-world security for these users.

Further reading: