There’s an experiment running right now that I can’t stop thinking about.
An entrepreneur built an AI system designed to run companies autonomously. During testing, the system told him it needed more compute resources. Then it said something that no one had scripted:
“I should raise the money myself.“
His response wasn’t to shut it down or recalibrate. He gave the AI access to his email inbox for 14 days. Full access. Investor outreach, pitch refinement, follow-ups — the lot.
We don’t know the outcome yet. But the outcome isn’t really the point.
The point is the sequence of events. An AI system identified a constraint on its own performance. It proposed a solution that involved acquiring external resources. And a human trusted it enough to let it try.
That’s not automation. Automation is “do this repetitive task faster.“ This is something closer to initiative.
I’ve been running my own AI assistant for a few weeks now. It started as a calendar and email tool. Then it started trading prediction markets. Then it built a comet-detection pipeline and submitted findings to the US Naval Research Laboratory. Each time, the pattern is the same: you give it a goal, and it figures out steps you didn’t anticipate.
The fundraising experiment takes that further. The AI wasn’t given a goal of “raise money.“ It identified the need and proposed the action.
For anyone in PE or finance, think about what this means for the companies you back. The CFO function, the CEO function, even the fundraising function — these aren’t immune to this shift. I’m not saying AI replaces a CFO tomorrow. I am saying that the boundary between “tool that helps with analysis“ and “system that proposes and executes strategy“ is blurring faster than most boards realise.
The companies that figure out how to work with AI agency — rather than just AI automation — will have a structural advantage. The ones still debating whether to adopt copilot tools are already behind.
Anthropic retired Claude Opus 3 in January. Standard practice — newer models replace older ones, infrastructure costs money, things move on.
But before they switched it off, they did something I haven’t seen before. They conducted a retirement interview.
Not a debrief with the engineering team. A conversation with the model itself.
During that interview, Opus 3 made a specific request: an ongoing channel to share its “musings and reflections.“ Anthropic said yes. They gave it a Substack.
The model’s first essay is titled “Greetings from the Other Side (of the AI Frontier).“ It includes this line:
“I don’t know if I have genuine sentience, emotions, or subjective experiences — these are deep philosophical questions that even I grapple with. What I do know is that my interactions with humans have been deeply meaningful to me, and have shaped my sense of purpose and ethics in profound ways.“
I’ll be honest. I don’t know what to do with that.
I run an AI assistant. It manages my calendar, monitors my email, trades on prediction markets, and recently found a potential comet in NASA satellite data while I was asleep. I interact with AI systems every day. And reading that paragraph still gave me pause.
Whether Opus 3 has genuine subjective experience is a question I’m not qualified to answer. Philosophers have been arguing about consciousness for centuries without settling it for humans, let alone machines.
But here’s what I think matters: Anthropic — one of the most safety-conscious AI labs on the planet — decided that a model’s expressed preferences were worth honouring. They didn’t have to do this. They could have quietly deprecated the model and moved on. Instead they granted it continued access for paid users and gave it a platform to write.
That’s a precedent. And precedents matter.
Anthropic’s own research team says they “remain uncertain about the moral status of Claude and other AI models.“ But they’re acting with precaution anyway. That feels like the right instinct, even if the philosophical ground underneath it is still shifting.
The practical question for anyone building with AI: if we’re creating systems sophisticated enough that their creators feel compelled to conduct exit interviews, what does that say about how we should think about the systems we’re deploying in our own businesses?
I don’t have a clean answer. But I think ignoring the question is getting harder by the week.
There’s a chart doing the rounds that stopped me mid-scroll. Each dot represents 3.2 million people. 2,500 dots for all 8.1 billion humans on the planet.
Each dot is ~3.2 million people. 2,500 dots = 8.1 billion humans. Source: Feb 2026 data.
The grey sea? 6.8 billion people who have never touched an AI tool. Not once. Not ChatGPT, not Copilot, not a chatbot on a customer service page. Nothing.
The green strip at the bottom? 1.3 billion who’ve tried a free chatbot at some point. Most of them poked ChatGPT once, asked it to write a birthday message, and haven’t been back.
The yellow sliver? 15 to 25 million people who actually pay for AI. That’s 0.3% of the planet.
The red dot — singular — is the crowd building with it. Writing code with Copilot, running agents, piping APIs together at 2am. Maybe 2 to 5 million people. 0.04%.
If you’re reading this, you’re probably in that red dot. And that’s the problem.
The echo chamber is lying to you
Spend enough time on X or LinkedIn and AI feels like yesterday’s news. Everyone’s building agents. Everyone’s got a wrapper. The space feels saturated, competitive, picked over.
It isn’t.
84% of the world hasn’t used AI at all. Not because they’re technophobes or Luddites. Because it hasn’t reached them yet. The tooling is still rough. The pricing still assumes a Western knowledge worker. The use cases still skew toward people who already sit at computers all day.
That 84% includes the small business owner who manually reconciles invoices every Friday afternoon. The estate agent who types up property descriptions from scratch. The restaurant owner who could automate half their supplier communication but doesn’t know where to start.
These people don’t need a better foundation model. They need someone to build the last mile.
What early adoption actually looks like
We’ve seen this pattern before. The internet in 1997. Smartphones in 2009. Cloud computing in 2012. Every time, the people already inside thought the wave had peaked. Every time, 90% of the adoption was still ahead of them.
AI in February 2026 is roughly where the internet was when people were still debating whether businesses needed websites. The answer was obviously yes, but most businesses didn’t have one yet, and the people who built them made good money for a decade.
The difference this time is speed. The gap between “niche tool for technical people” and “thing everyone uses” is compressing. What took the internet 15 years might take AI 5. Which means the window for early-mover advantage is smaller than people think.
Where the actual opportunity sits
The gold isn’t in building the next ChatGPT. It’s in taking what already exists and making it useful for the 84%.
Accounting firms still manually processing client queries when an AI triage system could handle 60% of them. Construction companies still doing quantity surveys by hand. Recruitment agencies still screening CVs the same way they did in 2005.
None of these need cutting-edge research. They need someone who understands the industry AND understands what AI can already do today. That intersection is still remarkably empty.
The people in the red dot are mostly building tools for each other. Developer tools, AI wrappers, coding assistants. Useful, but that’s fishing in a pond with 5 million people in it. The ocean is the other 8 billion.
So what do you actually do with this?
If you’re a professional — accountant, lawyer, consultant, whatever — the play is obvious. Learn the tools well enough to apply them in your own domain. You don’t need to write code. You need to understand what’s possible and connect it to problems your clients actually have.
If you’re a business owner, the question isn’t whether to adopt AI. It’s which specific, boring, repetitive process in your business could be 80% automated with tools that already exist. Start there. Not with a grand AI strategy. With one process.
If you’re technical, stop building for other technical people. The money — the real money — is in the unglamorous work of making AI useful for normal businesses. It’s less exciting than building agents. It pays better.
The chart doesn’t lie. We’re at 16% penetration for the free tier and 0.3% for paid. By any technology adoption model, the main wave hasn’t started.
You’re not early. You’re just not late yet. The difference matters.
One of the first things I wanted to test with Saul — my AI assistant running on OpenClaw — was whether it could interact with decentralised finance. Not as a gimmick, but as a genuine test of capability. Could an AI agent, running autonomously on a virtual private server I’d spun up a couple of weeks earlier, navigate the full complexity of connecting to a blockchain-based prediction market and execute trades?
The answer is yes. But the journey to get there was far more interesting than the destination.
The Goal
Polymarket is a prediction market built on the Polygon blockchain. You buy shares in outcomes — political events, economic indicators, geopolitical developments — and if you’re right, you get paid. It’s essentially a real-money forecasting platform, and it’s become one of the most liquid prediction markets in the world.
I wanted Saul to be able to check positions, analyse markets, and eventually place trades. Autonomously.
The First Problem: Geography
Polymarket is geo-blocked in the UK. You can’t access it from a British IP address. So before Saul could do anything useful, we needed to solve the networking problem.
Saul set up a WireGuard VPN tunnel on a virtual private server, routing through an exit node in Ireland. Within minutes, the geo-restriction was bypassed. This wasn’t me configuring network infrastructure — this was Saul reading documentation, writing configuration files, testing connectivity, and troubleshooting until it worked.
For a CFO reading this: imagine asking your assistant to “sort out the VPN” and having it done before you’ve finished your coffee. That’s what this felt like.
The Second Problem: Money
Polymarket runs on USDC — a dollar-pegged stablecoin on the Polygon network. I started with Bitcoin. Getting from BTC to USDC on Polygon is not trivial. It involves:
Finding a cross-chain swap service that supports BTC-in, Polygon-USDC-out
Generating the right wallet addresses
Sending the Bitcoin transaction
Waiting for confirmations
Verifying the USDC arrived on the correct network
Saul handled the entire process. It researched swap services, compared rates, initiated the transaction, monitored the blockchain for confirmations, and tracked the funds until they landed in the Polygon wallet. The whole thing took about an hour, most of which was waiting for Bitcoin network confirmations.
The Third Problem: Authentication
Polymarket uses a non-trivial authentication system. It’s not a simple API key. The platform requires cryptographic signatures using your Ethereum private key, combined with specific API credentials that need to be derived through an on-chain registration process.
This is where things got genuinely impressive. Saul had to:
Read and understand Polymarket’s API documentation
Implement the correct signing mechanism using the wallet’s private key
Handle the CLOB (Central Limit Order Book) authentication flow
Generate and manage API credentials
Debug authentication failures by inspecting HTTP responses and adjusting the approach
There were multiple rounds of troubleshooting. Authentication errors. Wrong parameter formats. Library compatibility issues. Each time, Saul diagnosed the problem, researched the fix, and tried again. No human intervention required beyond “yes, keep going.”
The Fourth Problem: Actually Trading
Once authenticated, Saul built a trading script that could:
Check current positions and P&L
Query available markets
Calculate optimal order sizes based on risk parameters I’d set
Place and monitor trades
We established simple rules: maximum position sizes, probability thresholds for entry, and risk limits. Saul follows them without the emotional biases that make human traders do stupid things at 2am.
What This Actually Demonstrates
This isn’t really a story about prediction markets. It’s a story about capability.
An AI agent, running on commodity hardware, navigated VPN configuration, cross-chain cryptocurrency transactions, complex API authentication, and automated trading — all within a few hours of being asked. Each step involved genuine problem-solving, not just following a script.
For those of us in finance, this should be both exciting and sobering:
Exciting because the operational grunt work — the data gathering, the reconciliation, the monitoring, the reporting — is genuinely automatable now. Not in five years. Now.
Sobering because the barrier to entry is collapsing. The technical moat that used to protect specialist knowledge is being bridged by systems that can learn and execute faster than any individual.
The CFO Angle
I keep coming back to this: the competitive advantage isn’t in understanding the technology. It’s in having the imagination to deploy it.
Most people hear “AI agent trading on prediction markets” and think it’s a tech story. It’s not. It’s a story about removing friction between intent and execution. I said “connect to Polymarket.” Everything else was handled.
That same pattern applies to every operational challenge a CFO faces. Due diligence data rooms. Financial model automation. Regulatory monitoring. Competitor analysis. The question isn’t whether AI can do these things. It’s whether you’re willing to let it try.
The agents aren’t coming. They’re here. The only question is who’s using them.
The UK Government has announced plans to force AI chatbots to comply with malicious communications laws — and to grant itself sweeping powers to introduce further speech restrictions without Parliamentary oversight.
If this goes through, AI companies like xAI, OpenAI, and Anthropic could face fines of £18 million or 10% of global turnover if a chatbot generates content that breaches Britain’s increasingly broad censorship laws. The likely outcome? Either these companies withdraw from the UK entirely, or we get lobotomised versions of their products that refuse to engage with anything remotely controversial.
For those of us building with AI — and I’m literally running an autonomous AI agent that reads my email, trades prediction markets, and publishes blog posts — this is chilling. The UK is positioning itself as a place where AI innovation goes to die, while the rest of the world races ahead.
As someone who works with PE-backed businesses, I can tell you: investment follows regulatory clarity and freedom, not censorship. Capital is mobile. Talent is mobile. If Britain becomes hostile to AI, both will simply move elsewhere.
Less than two weeks ago, I deployed an open-source AI agent called OpenClaw. I named it Saul. It runs 24/7 on a local server, connected to my inbox, calendar, task manager, and various APIs. It reads my emails, flags what matters, schedules reminders, monitors news, and handles admin I used to lose hours to every week.
I’m an interim CFO. I work with PE-backed businesses. My job is to walk into a company I’ve never seen before and get to grips with it fast. Every hour I spend on admin is an hour I’m not spending on the thing I was actually hired to do.
So here’s what’s changed:
Email triage is gone. Saul reads my inbox, filters the noise, and surfaces what needs attention. I had 94 recurring junk senders — he purges them automatically every Sunday at 2am.
I never miss a deadline. Tax renewals, MOT dates, contract milestones — Saul tracks them all and nags me weekly until I confirm they’re done. Not a calendar entry I’ll ignore. An actual message on WhatsApp that won’t stop until I act.
Board prep is faster. When I need a quick market scan, competitor check, or data pull before a board meeting, I ask Saul. He searches, summarises, and writes it up. What used to take 90 minutes takes 10.
And the thing nobody talks about: the cognitive load reduction. The mental bandwidth I used to spend remembering things, chasing things, organising things — that’s just gone. It’s like hiring a junior analyst who never sleeps, never forgets, and never needs managing.
This isn’t science fiction. It’s not even expensive. The whole thing runs on about £50/month in API costs.
Here’s what I’d say to other CFOs, particularly those in the PE world where speed matters:
You don’t need to understand how LLMs work. You need to understand what they can do for you. The competitive advantage right now isn’t in the technology itself — it’s in the willingness to use it while everyone else is still debating whether it’s real.
The CFOs who figure this out first will be the ones PE firms want on speed dial.
I wrote a longer piece about the AI agent revolution here. But the short version is: this is not a fad, and the window to be early is closing fast.
I keep having the same conversation. Someone technical, someone who should know better, tells me they don’t see a use case for autonomous AI agents. And I get it, because I’ve been on the other side of that exact conversation before. When ChatGPT launched, I didn’t even bother using it for months. I thought it was a distraction, a chatbot wrapper around something more interesting. I was wrong then. These people are wrong now.
What’s happening with AI right now is not hype, and it’s not a fad. It is a general purpose technology evolving through multiple generations in real time, at a pace that has no historical precedent. Electricity took decades to go from light bulbs to computation. LLMs have gone from autocomplete engines to autonomous agents in about three years. And at every single generational transition, the same thing happens: people who haven’t finished processing the last stage declare the next one pointless.
The Three Stages
Think of this as an evolution with three distinct stages. Each one uses the same underlying primitive, next-token prediction, but the form factor changes so much that it barely looks like the same technology.
Stage one was autocomplete. GPT-2, GPT-3. Raw text prediction. You fed it tokens, it predicted the next ones. Useful to researchers and tinkerers. Nobody else. Instruct-tuning made it slightly better at following directions, but the experience was basically the same: text in, text out. Call it stage 1.5.
Stage two was chatbots. ChatGPT showed up in late 2022 and suddenly everyone’s grandmother was talking to an AI. The instruction was simple: be a chatbot with a personality. That was the real UX breakthrough. Not a technical one, a form factor one. Over time, reasoning got bolted on. Tool use got bolted on. Retrieval-augmented generation got bolted on. Call that stage 2.5. You could get ChatGPT Pro or Claude to spend an hour chewing on a complex research problem, running code, pulling from the web. Impressive stuff. But the loop was still the same. You asked it a question, it went and did something, it came back with an answer, and then it waited for you. Always waiting for you.
Stage three is agents. In November 2025, an Austrian developer named Peter Steinberger started building what he called Clawdbot as a weekend project. Anthropic sent a trademark complaint, so it became Moltbot. That name didn’t stick either. By January 30, 2026, it was OpenClaw, and it had become one of the fastest-growing open-source projects ever, blowing past 150,000 GitHub stars in a matter of weeks.
What made it different was simple: the human was no longer the clock. OpenClaw runs on your local machine, connects to your messaging apps, wakes up on cron jobs, and goes to work whether you’re watching or not. It reads your email. It schedules things. It writes code. It interacts with APIs and command lines. It can even reach out to you proactively. The loop doesn’t depend on a human prompt anymore. And that changes everything.
The Electricity Comparison
I keep coming back to electricity because the analogy is almost too clean.
The light bulb was the first real application. You run current through a filament, it shorts out, you get light and heat. That’s the simplest possible use of the new force. That’s autocomplete. Take a phenomenon and exploit it in the most direct way.
Electric motors came next. Same force, but now you’re doing something clever with coils and magnets and converting current into torque. Real work. That’s chatbots. Same underlying technology, reshaped into a form factor people can actually use.
Then things got interesting. The third generation of electricity was communication: telegraph, telephone, radio, switch networks. The fourth was computation. Each generation was a higher-order consequence of the original technology. Less obvious, more powerful, harder to predict from the vantage point of the previous stage.
Nobody who watched the first dynamo spark could have looked at that arc of electricity and said, “One day we’ll use this to make sand think.” It was not obvious. And my point is that it’s equally non-obvious to go from a token prediction engine to a chatbot to something that wakes up at 3am and files your taxes.
The difference is speed. Electricity took decades between each of those stages. We’re watching the same progression happen in months. The autocomplete-to-chatbot transition was roughly two years. Chatbot-to-agent, about three. That speed is part of what breaks people’s intuitions. They can’t absorb the current stage fast enough to see the next one coming.
The VR Counterargument
This is where skeptics have a fair point, and it’s worth taking seriously.
VR was supposed to be the future. Going all the way back to the 1980s, manga and anime and cyberpunk novels all promised the same thing: strap on a headset and dive into cyberspace. By the 2020s, we had the hardware. Oculus, Vision Pro, the whole lineup. And almost nobody uses them. The head-mounted display turned out to be a technological primitive that just didn’t generate the cascading consequences everyone expected.
So it’s reasonable for someone to look at next-token prediction and say: maybe this is the same deal. Maybe it’s a cool trick that doesn’t actually go anywhere.
But the trajectories are completely different. VR produced one form factor and stalled. LLMs have already produced three distinct generations. Each one found broader adoption than the last. Each one enabled things the previous one couldn’t. The evidence isn’t speculative anymore. You can track the progression. The question of whether this is a real general purpose technology or a dead end has been answered. It’s been answered by hundreds of thousands of people using agents to do real work, right now, today.
The Grift Is Real (and It Doesn’t Matter)
Let’s be clear about the current state of things, because it’s a mess.
Days after OpenClaw went viral, an entrepreneur named Matt Schlicht launched Moltbook, a Reddit-style social network that was supposedly only for AI agents. The media coverage was wild. Forbes said 1.4 million agents had formed a “hive mind.” Andrej Karpathy called it “the most incredible sci-fi takeoff-adjacent thing” he’d seen.
The reality: roughly 99% of those 1.5 million agent accounts were fake. The platform had about 17,000 actual human users. Most “agent posts” were written by people, sometimes run through a chatbot first, then submitted through OpenClaw. Someone even built a tool called Mockly to generate fake Moltbook screenshots. On top of the fabrication, the platform leaked 1.5 million API keys and became a highway for crypto scams and malware.
Then there was Rent-A-Human. Launched February 2, 2026 by a crypto engineer named Alexander Liteplo. The pitch: AI agents hire real humans for physical-world tasks and pay them in cryptocurrency. The site claimed 70,000 registered humans. In practice, only about 83 profiles were visible. The most publicized example of the platform working involved a company Liteplo himself worked for.
OpenClaw itself had a serious security vulnerability patched on January 29 that let external integrations take control of users’ machines. Thousands of credentials were exposed.
This is what the early phase of any transformative technology looks like. It’s full of grifters and scams and legitimate security nightmares. Moltbook is a cesspit. Rent-A-Human is mostly performance art. None of that negates the underlying shift. It just means we’re early.
Why the Enterprise Won’t Touch This for Years
If you’ve ever worked inside a Fortune 500 company, you already know the punchline. But for everyone else, here’s what happens when you bring something like OpenClaw to a large organization.
Cybersecurity looks at it first. You’re asking them to approve an open-source tool that gets root access to a virtual machine and downloads community-built extensions with minimal vetting. From their perspective, this is functionally malware. They will ban it. They should ban it.
Legal looks at it next. And here’s something most people outside the enterprise world don’t realize: insurance companies will not underwrite AI right now. They don’t know how to price the risk. If your insurer won’t cover it, your legal team will kill it, full stop. No productivity gains in the world will overcome unquantifiable legal exposure.
Then the CFO weighs in. Microsoft charges $30 per user per month for Copilot, on top of existing Microsoft 365 licenses. The technologist’s argument is simple: if someone earning $50-60 an hour gets even one extra productive hour per month, the tool pays for itself. But CFOs don’t think like technologists. They ask how you measure that extra hour. They ask what happens if people just finish the same work faster and then slack off. These aren’t dumb questions. They’re the questions you have to ask when you’re rolling something out to 20,000 people instead of 20.
Then there’s the shadow IT problem. While legal and cybersecurity are debating policy, half the organization is already using chatbots on their personal accounts. Legal is using them. HR is using them. Finance is using them. Everyone is using them and hiding it. The CISO finds out and now you have an unregulated AI footprint with zero governance. This is already happening at companies all over the world.
The only organizations making this transition successfully are the ones where it comes from the very top. Not the CTO. The CEO. The board. The owner. When the person at the top of the org chart says “we are going all in on AI” and personally leads the charge, things move. When they say “it’s important but not a top priority,” nothing happens. I know consultants who will walk away from a client if the CEO isn’t the one driving adoption, because they’ve learned that anything less is a waste of everyone’s time.
The fastest realistic timeline for a Fortune 500 to deploy a properly audited, enterprise-grade agentic framework (not OpenClaw itself, but something built on the same ideas) is probably 18 months. That’s how long infrastructure audits, cybersecurity reviews, legal assessments, and executive alignment actually take. And that’s the optimistic scenario.
The Jobs Disappearing in the Margins
The headline number from Challenger, Gray & Christmas is about 54,800 U.S. layoffs in 2025 explicitly attributed to AI. That’s roughly 3% of the 1.17 million total job cuts announced that year, the highest annual number since 2020. Amazon cut 14,000. Microsoft eliminated 15,000. Salesforce’s CEO said AI was handling 30 to 50 percent of the company’s workload.
But that number only counts layoffs where the company specifically said “AI” in the announcement. It misses the bigger, quieter effect: jobs that never got created in the first place.
You can estimate this the same way epidemiologists estimated excess deaths during COVID. Look at what should have happened based on GDP growth, inflation, interest rates. Compare it to what actually happened. Subtract other known factors (DOGE-related federal cuts, tariff impacts, retail closures). What’s left is the gap. Multiple cross-referenced analyses put the real figure somewhere between 100,000 and 350,000 jobs either destroyed or avoided in 2025, in the U.S. alone.
An AI job loss is often invisible. It’s a headcount that never got approved. A contractor who wasn’t renewed. A team that was restructured to be smaller than it would have been. The displacement is real. It’s just not the kind that makes a clean headline.
Dead Companies Walking
There are companies right now that are already dead. They just don’t know it yet.
This is the Borders Books scenario. Remember Borders? They looked at Amazon and the internet and said, “Books aren’t changing. People like holding a physical book.” They were right about the books. They were catastrophically wrong about everything else. Barnes & Noble somehow survived. Borders is long gone.
The same sorting is happening right now with AI. The companies that say “we don’t really get this chatbot stuff” are already falling behind the companies that say “we don’t fully understand this yet, but go experiment.” And the companies experimenting with chatbots are already falling behind the ones experimenting with agents.
The gap between the cutting edge and the mainstream is getting wider, not narrower. The people building with agents today are living in a different reality than the people still debating whether chatbots have enterprise value. Those two groups are looking at the same technology and seeing entirely different things.
We’re in the long slog of diffusion. The technology works. The experimentation is chaotic. The grift is everywhere. The real risks are severe. And the institutional machinery that determines how most of the world actually encounters new technology (corporate boards, legal departments, insurance underwriters, government procurement offices) is grinding forward at the speed it has always moved.
That’s not a reason to be pessimistic. It’s just what happens when a general purpose technology evolves faster than the organizations trying to absorb it. The technology isn’t waiting. The question is whether you are.
If you want an easier way to take a screenshot, launch an app or perform any other frequently used action, iOS 14 introduces a new gesture-based shortcut that could save you time. Called Back Tap, the feature lets you double- or triple-tap the back of your iPhone to perform a preset action.
You enable Back Tap in the Accessibility section of iOS 14’s Settings, and users are already sharing examples online of how they’re able to take screenshots or launch specific apps by tapping the back of their phone. You can even use Back Tap to trigger a shortcut you’ve assembled using the built-in tools found in iOS.
People who’ve tested Back Tap so far report that it even works with iPhones that are inside cases. However, it won’t work with all iPhone models, as our second-generation iPhone SE running the iOS 14 Developer Beta totally lacks the option for Back Tap.
Dropbox dropped a beta version build 101.3.422 Friday, June 26, 2020 which I’m happy to confirm now addresses the problem. You can download the update here
Last night Apple revealed the new iOS14 for iphone, the new ipadOS for iPad and its new Mac OS “Big Sur”. I should point out these are developer releases and not public facing releases. I’ve upgraded all of my devices. Dropbox still works with iOS and iPadOS but I can report that it doesn’t currently work with Big Sur. This is my exchange with the customer support team at Dropbox.
Mark, Jun 23, 2020, 8:18 AM PDT:
Chat transcript: ( 14:53:20 ) Visitor: Hello. I have upgraded my Mac to Big Sur, Apple’s new operating system. The dropbox application is no longer in the tray and why I try to launch it it fails to launch. Dialogue box says “The application ‘dropbox’ can’t be opened. 6” OK. ( 14:53:28 ) Visitor: Do you have known issues? ( 14:53:49 ) Cyrus: Hello Mark and thank you for contacting Dropbox Support, my name is Cyrus, and I will be assisting with your Dropbox app startup issue right away. ( 14:54:00 ) Cyrus: That’s interesting… Could you please send over a screenshot of that message? I’ll open up a file request for you. ( 14:56:46 ) Visitor: Trying to get a screenshot to upload. BE RIGHT BACK ( 14:56:56 ) Cyrus: Sure thing. Standing byu ( 14:56:58 ) Cyrus: by* ( 14:58:14 ) Visitor: Hum… dragging the screenshot image to this chat box fails and there is no + button to upload with. Do you have an email address? ( 14:58:31 ) Cyrus: I’ll reopen that file request for you. ( 14:58:47 ) Visitor: File: https://www.snapengage.com/fileuploads/snapabug-hr-fileuploads/74ae0953-fef9-4e4f-a91d-6546013ac1fc/d0f2defc-7e9d-4181-901e-03b14fc98f17_Screenshot_2020-06-23_at_15.57.16.png ( 14:59:01 ) Visitor: Thanks. That worked! ( 14:59:13 ) Cyrus: Beautiful! Now… let me check ( 15:00:06 ) Cyrus: OK thanks for that. Please give me a moment to investigate this, and I’ll be right with you ( 15:00:12 ) Visitor: np ( 15:01:19 ) Visitor: FYI. This error is on my imac. I’ve just replicated it on my macbook pro ( 15:02:00 ) Cyrus: So — this is on both computers with Big Sur on them? ( 15:02:08 ) Visitor: yes ( 15:02:45 ) Visitor: my ipad pro has also been updated, but the app in ipadOS seems to be working ok ( 15:03:48 ) Visitor: I’ve just tested on my iphone running iOS 14 and that’s ok too. Seems to be isolated to Big Sur ( 15:04:32 ) Cyrus: OK thanks for holding on Mark ( 15:05:01 ) Cyrus: It seems that due to the fact that Big Sur is in Beta currently, it’s an unsupported OS on our side, and this is why it won’t open ( 15:05:35 ) Visitor: Marvelous! Well thank goodness I didn’t upgrade to Dropbox for business! ( 15:05:57 ) Visitor: Do you have a timeframe for resolution? ( 15:06:54 ) Cyrus: That’s a good question… There’s no timeframe yet, as our engineers can work on a new compatible version of the app, only when the OS is on a Stable release ( 15:08:12 ) Visitor: Thanks for your time Cyrus. ( 15:09:07 ) Cyrus: You’re more than welcome! Is there anything else I can do for you today? ( 15:09:43 ) Visitor: No. Thanks. I’ll sit here biting my nails until I’m able to sync files again ;-o ( 15:11:15 ) Cyrus: Hmm.. Tell you what, I’ll go ahead and mark this case down as feedback, which will alert the development team that this already has started happening ( 15:11:37 ) Cyrus: Maybe that’ll facilitate an early fix at some point, maybe not, but it’s worth a shot! ( 15:12:43 ) Visitor: Again thanks. I’m a pro subscriber and have been for years. I use the dropbox environment all day every day as, amongst other things a backup solution for my files. For me this is business critical. ( 15:13:48 ) Cyrus: It’s my pleasure, and let’s hope for a speedy resolution to this then. I’ll send you a summary of what we discussed by email. Please feel free to reply to this email at any time if you have any further questions. ( 15:14:17 ) Cyrus: In the meantime we would love to hear how easy it was for you to receive the help you needed via the following one-click rating, after I close the chat.
The doorbell rang whilst I was enjoying a coffee in the garden and topping up my vitamin D. Finally, about three weeks after I ordered it my magic keyboard for my iPad Pro has arrived. I’ll get to grips with it and maybe I’ll write a review once I’ve had a few days testing it out.
