| author | Alan Dipert
<alan@tailrecursion.com> 2026-02-21 16:28:41 UTC |
| committer | Alan Dipert
<alan@tailrecursion.com> 2026-02-21 16:28:41 UTC |
| parent | 47da6154e7de52ed1c6aaae56845215a7510ef2c |
| md/_GridCalc.md | +1 | -1 |
diff --git a/md/_GridCalc.md b/md/_GridCalc.md index da364ca..30797b0 100644 --- a/md/_GridCalc.md +++ b/md/_GridCalc.md @@ -57,7 +57,7 @@ Spreadsheets are reactive systems. When you change a cell, everything downstream Technically, spreadsheets on phones deliver this. In practice, though, traditional spreadsheets are punishing as mobile interfaces. You tap into a formula bar. You scroll sideways. You lose context. The sheet is there, but the program is buried, and editing an infix formula on a phone keyboard can be particularly frustrating. Mobile spreadsheets are tolerable for data entry or viewing, but frustrating for scratch modeling. -In GridCalc, the program is always visible because the grid *is* the formula. It economizes the creation of formulas on the go. Every input, and every operation, inhabit a visible cell. The grid provides a coordinate system that can be used to refer to previous values, linking them to new calculations. Much of the power of a spreadsheet is thus delivered directly to the mobile user. +In GridCalc, the program is always visible because the grid is the formula. It economizes the creation of formulas on the go. Every input, and every operation, inhabit a visible cell. The grid provides a coordinate system that can be used to refer to previous values, linking them to new calculations. Much of the power of a spreadsheet is thus delivered directly to the mobile user. ## UI evolution