fiko

Sessions

1. Six sessions are open and logs is shown. A deploy is running in another one.
2. Every session is in one list. Under it is a live preview of the selected session and its state: working.
3. The list narrows with each letter typed.
4. Only deploy is left. Its preview is live, and its state changes to idle when the work is done.
5. A tap, and deploy is shown.

Quick access

1. A phone screen has little room for menus, and fiko has many actions.
2. Quick access is one list that holds all of them.
3. Pages, sessions, tabs, settings: every action is here, in groups.
4. Part of an action's name is enough: the list narrows as it is typed.
5. Only Theme is left.
6. A tap, and the Theme settings open over the session.

Terminal

1. True colour, text styles and box drawing, drawn as a desktop terminal draws them.
2. A phone keyboard has no Esc, Tab or Ctrl. The bar over it has them.
3. Tab from the bar completes the file name: app.yml.
4. A full-screen editor runs as it does on a desktop, colours and all.
5. The bar has more pages. This one has the arrow keys, and they move the cursor.
6. Esc is on the bar as well. The editor is closed, and the shell is back.

Files

1. A server's folders, in an SFTP tab beside the terminal sessions.
2. A tap opens a folder. logs holds two files.
3. A tap picks a file. A second tap, or a hold, opens its actions: open, download, rename, move, delete.
4. A text file opens in fiko: README.md.
5. Select puts a circle before every name.
6. Two files are selected. They can be downloaded or moved together, or their paths copied.

Servers

1. A server is saved once. After that it is opened with a tap.
2. Servers lists the saved ones. Add starts a new one.
3. A server is a name, an address and a way to sign in.
4. The name is what the list shows: staging.
5. The address is written as for ssh: user, host and, if needed, a port.
6. Four ways to sign in: password, key, keyboard-interactive, or none.
7. Key signs in with a key kept in fiko. This one is named ed25519.
8. Saved. staging is in the list, to open as a terminal or as files.

SSH keys

1. An SSH key is a pair. The private key signs in and stays in fiko; the public key is given to the server.
2. Keys are kept with the servers: SSH Keys, under the list.
3. One pair is here already. Generate makes another.
4. A new pair, made on the phone: ed25519-2.
5. A tap on it shows the public key, the line a server is given.
6. Copy puts the public key on the clipboard. The private key does not leave fiko.

Clipboard

1. A picture was copied in another app: latency.png is on the clipboard.
2. In a terminal session, a command is begun: ls -lh and a space.
3. Paste is on the second page of the bar over the keyboard.
4. A terminal takes text, not pictures. fiko shows the picture and where it goes on the server: /tmp/latency.png.
5. Upload sends it to the server's temporary folder.
6. The path is typed at the cursor, where the picture itself could not go.
7. The command runs on it. A program in the session can read the picture by that path.

Alerts

1. A deploy is started in one session. It will take a while.
2. It runs. Nothing needs watching here.
3. Another session is opened, a log. The deploy goes on out of view.
4. The deploy ends and says so. fiko shows a toast with the session's name and its message: Deploy finished: web v2.4.9.
5. Show goes to that session: deployed.

Theme

1. A terminal in fiko's black theme, with a blue accent.
2. Theme is in Quick access, with the other settings.
3. Three tabs: Theme, Font and Terminal. The preset is Black.
4. White is chosen, and the whole of fiko changes at once, behind the panel too.
5. The accent goes from Blue to Green: headings, the chosen tab, the cursor.
6. Under Terminal, the text scale is raised two steps, and the text behind grows.
7. Save keeps it. The same session, in white, with larger text.

Mouse

1. This program is run with a mouse: its rows are clicked. On the bar, the key reads Touch: a finger is a finger.
2. One press, and it reads Mouse. The terminal shows a pointer.
3. The screen is a touchpad now: the finger slides anywhere, the pointer goes the same way, and the row under it lights up.
4. A tap clicks where the pointer is, not where the finger is. cache is running.
5. A slide to the next row, a tap: mail is stopped.
6. The key again, and a finger is a finger. The pointer is gone.

Find

1. A log runs past. Somewhere in it are the requests that failed.
2. Find is on the bar over the keyboard.
3. 500 is typed. Every match in the scrollback is marked, and counted.
4. The arrows beside the count step from one match to the next.

Scrollback

1. Output runs past faster than it can be read.
2. A drag down goes back through it.
3. The lines from two minutes ago are still here. How many are kept is a setting.
4. A few flicks, and the newest lines are back.

Rename

1. README.md should end in .txt.
2. A hold on the file opens its actions. Rename is one of them.
3. The name opens in a box, ready to change.
4. The last letters are replaced: README.txt.
5. Save, and the file has its new name on the server.

Move

1. notes.txt is in web. It belongs in logs.
2. A hold on the file, and Move.
3. Only folders are listed now, to pick the one it goes to.
4. Inside logs, Move Here.
5. notes.txt is gone from web.
6. It is in logs, beside the two logs.

Select many

1. Three of these files belong in another folder.
2. Select puts a circle before every name.
3. The three are tapped: 3 selected.
4. Move works on all of them. The folder is picked once.
5. They are moved one after another, with the count shown.
6. All three are gone from web.

Upload

1. This folder is on the server. Upload, under the list, sends a file from the phone to it.
2. Android's own file list opens, and the file to send is tapped: release-notes.txt.
3. Back in fiko, the upload shows its progress over the list.
4. release-notes.txt is in the folder on the server.

Download

1. notes.txt is on the server. It is wanted on the phone.
2. A hold on the file, and Download.
3. Android asks where to keep it. A folder is chosen: fiko-demo.
4. Android asks once whether fiko may write to that folder.
5. Back in fiko, the download shows its progress over the list.
6. Saved on this device: the file is on the phone.

First connection

1. A server is opened for the first time. fiko has not seen its key.
2. The server is tapped in Servers.
3. Before anything is sent, fiko shows the server's host key and asks. The address is covered in this clip.
4. The fingerprint is compared with the server's own. They match: Trust.
5. Trusted. The key is remembered, and the connection goes on.

Known hosts

1. Every host key that was trusted is kept in a list.
2. Known Hosts is under the list of servers.
3. One host is remembered, with its key type and fingerprint. Its address is covered in this clip.
4. A hold on it offers Info and Forget. A forgotten host is asked about again.
5. Info shows the whole key as one line, to copy.

Add to a server

1. The public key is on the clipboard. A server keeps the public keys it accepts in one file.
2. In a session on that server, the line that adds to the file is begun.
3. The bar over the keyboard has a second page, with Paste.
4. Paste puts the whole public key on the line.
5. The line is finished: it adds the public key to .ssh/authorized_keys.
6. One public key is in the file. The server now lets its private key sign in, with no password.

Sign in with the key

1. The server has the public key. The private key is on the phone, in fiko.
2. staging is a saved server. Addresses are covered in this clip.
3. A hold on it, and Edit shows how it signs in.
4. Sign in with is set to Key, and the key is ed25519-2, the pair made earlier.
5. Back in the list, the server is tapped.
6. fiko connects and signs in with the private key.
7. The shell is open. No password was asked for.

Away from fiko

1. A deploy is started in a session.
2. It runs. This time fiko itself is left.
3. Another app is in front. The session stays open in the background.
4. The deploy has ended. In Android's notification panel, fiko's notification has the session's name and its message.
5. A tap on it opens fiko at that session: deployed.