A simple autocomplete glitch in Excel Online has revealed something deeper about the limitations users accept every day. One user on Linux, working in the Spanish interface, found that COUNT refused to appear in the function suggestions while COUNTIF and COUNTA showed up without issue. They typed it manually in English and Spanish, wrote the full formula from memory, and still got nothing. This is not a dramatic failure, Excel Online still works for most tasks, but it is the kind of friction that quietly erodes trust in a tool. When a basic function like COUNT becomes a puzzle, the user stops being productive and starts troubleshooting. That is not how software should treat its users.
The practical takeaway here is straightforward: Excel Online, for all its accessibility, remains a browser-based compromise. Microsoft has done impressive work bringing spreadsheet functionality to the web, but edge cases like this one expose the gaps. The user's choice to use Excel Online over LibreOffice on Linux is understandable, familiarity and ecosystem lock-in are powerful forces, but it also means accepting a version of the tool that is not fully in their control. Autocomplete is a convenience, not a guarantee. When it fails, the user must fall back on manual entry, workarounds, or community forums. That is a fragile workflow for anyone who relies on spreadsheets for real work.
What this situation really signals is a broader opportunity. If a user on Linux is willing to work around Excel Online's quirks rather than switch to a native alternative, they are clearly invested in the spreadsheet experience. Yet the tool is still asking them to adapt to its limitations rather than adapting to their needs. An AI-native spreadsheet would not require the user to hunt for a missing function or guess at syntax. It would understand intent, offer the correct formula based on context, and handle localization without breaking. The gap between what users expect and what legacy tools deliver is exactly where innovation can step in, not by promising a revolution, but by solving the actual problems people face every day.
For this user, the immediate fix is likely a browser cache clear, a language pack update, or a switch to English interface temporarily. But those are band-aids. The real solution is a tool that does not treat a missing autocomplete suggestion as a user problem. Until then, the COUNT function will stay hidden for some, and the workaround will remain a test of patience, not skill.