The Journey of a File
Every file sent through SecurityNet follows exactly the same journey.
The user doesn't need to think about it.
But quite a lot happens between pressing Send and the document appearing safely on someone else's computer.
It all begins with an ordinary file.
Perhaps it's a Word document.
A spreadsheet.
A PDF.
Whatever it happens to be, SecurityNet never changes the original.
Instead, it creates a secure copy specifically for transmission.
That copy is encrypted before it ever leaves your computer.
From that moment onwards, the information travelling across the Internet is no longer the original document.
It's encrypted data.
Anyone intercepting it would simply see encrypted content.
Not the document itself.
Once encrypted, the file is given to SecurityNet's communication engine.
Earlier I explained how two computers find each other.
Now that they have found each other, the encrypted file begins its journey.
Wherever possible, it travels directly between the two computers.
If the Internet prevents that, the encrypted data is relayed.
Either way, the contents remain encrypted throughout the journey.
Eventually the encrypted file reaches its destination.
Only then does the receiving computer decrypt it.
Not the mediator.
Not the relay.
Only the authorised recipient.
The original document is then recreated on the recipient's computer.
At that point SecurityNet's responsibility is largely complete.
The information has arrived safely.
What happens next belongs to the user.
They may decrypt it
Read it.
Move it.
Back it up.
Delete it.
Those decisions are theirs.
One small design decision illustrates how testing influenced the final product.
Imagine someone sends you a document called ABC.docx.
A few days later they send an updated version with exactly the same filename.
Originally, SecurityNet simply recreated the newer document.
In doing so, it quietly replaced the earlier version.
Nothing had gone wrong.
The software was doing exactly what I had designed.
Testing showed me something I hadn't considered.
Users often need both versions.
So the design changed.
Before creating the new document, SecurityNet now preserves the previous version by renaming it to include the original date.
The latest version keeps its expected name.
The earlier version remains available if the user needs it.
Sometimes the smallest design changes protect users from the biggest frustrations.
Sending a file isn't really a single action.
It's a carefully managed journey.
Encrypt.
Find.
Transfer.
Receive.
Decrypt.
Protect.
Then step aside and let the user take control.
Every stage has one purpose.
Together they create something that feels remarkably simple.
Perhaps that's how good engineering often works.
The user sees one button.
Behind that button is an entire sequence of carefully designed decisions.
