A native app is on the way Coming soon

What a native app adds

A web page can already fill the screen, hold the display awake and install to a home screen. These four are the things it genuinely cannot do, and they are the reason the app is worth building at all.

• Planned

  A home-screen widget

  Block height and price sitting on the home screen next to everything else, without opening anything. A web page cannot draw outside its own window; a native app can.

• Planned

  Alerts while you are away

  A notification when a block milestone lands, when the price crosses a level you set, or when mempool fees finally drop. This needs code that runs while the app is closed, which is the one thing a browser tab is designed never to do.

• Planned

  Proper always-on display

  Phones with an always-on screen expose it only to native apps. The web app has to keep the display fully lit instead, which works but costs more battery than it should.

• Planned

  History that lives on the device

  Charts kept locally rather than refetched, so the app opens with something on screen immediately and survives a patchy connection.

How it is being built

In Flutter, one codebase for both iPhone and Android. That choice was made at the start of this project, not retrofitted: the Flutter shell has been sitting in the BlockClock repository since day one, waiting for the web side to be worth extending.

Two things have to happen before it reaches a store, and neither is a coding problem: an Apple developer account, which costs money every year, and Google Play's one-off registration. Those come when the app is ready, not before.

What to use today

The web app. Added to a home screen it opens on its own icon, fills the screen with no browser bar, and keeps the display awake — which covers the reason most people want a clock app in the first place. It costs nothing and there is no store involved.