Takeaways Took Two Months to Reach the App Store

A calendar beats a stopwatch

A promising conversation has an unfortunate habit of becoming a vague recollection. You remember that somebody said something worth keeping. The somebody survives; the something disappears. William Sayer built Takeaways around that small, familiar failure. The more useful surprise is how long it took him to put a first version into people’s hands.

Anything’s customer story, dated June 10, 2025, says Sayer built V1 with Create in two months and launched on the App Store that June. Create was the predecessor to Anything. The account describes a non-developer who had previously climbed Everest, Manaslu and Ama Dablam, then turned to making software.

Two months is a refreshingly ordinary unit of time. It can hold decisions, revisions and the discovery that the button everyone admired does not do quite what anyone needs. For a founder deciding what to promise, that makes it useful. A dazzling demonstration measures how quickly something appears. A launch account reaches a more consequential destination.

Source: Anything’s June 10, 2025 customer story.

The details worth keeping

The product’s initial job was compact: save an insight from a conversation, associate it with a person, and set a reminder to revisit it or act. Those three functions are described in Anything’s customer story.

Imagine a friend mentioning an ambition over lunch. A note preserves the detail; a person attached to it preserves the context; a reminder creates an occasion to follow up. This is an illustration of the product idea, rather than a reconstruction of Sayer’s own conversations. Memory becomes useful when it finds its way back into conduct.

That tight scope gives the timeline meaning. “An app” can mean almost anything, from a single useful screen to a sprawling business. Here, the work has a legible centre. Someone building a similarly focused first release has a comparison to examine. Someone planning a complex marketplace would need a much closer match before borrowing its calendar.

Source: Product features in the customer story.

When the first tools stopped fitting

According to Anything’s account, earlier no-code tools helped Sayer test ideas, but felt limiting as his requirements grew. He wanted more flexibility and moved to Create. The story does not name those tools or document a feature-by-feature comparison.

The useful question for another builder is therefore specific: where does your own workflow get stuck? Perhaps an interaction is awkward to express, or a change takes too much rebuilding. Establish the actual obstacle before deciding that a different tool will remove it. Sayer’s experience supplies a reason to investigate, rather than a verdict on every visual builder.

Changing tools also leaves the product decisions with the person making the product. Someone must decide what a saved insight contains, how a person is identified, and what a reminder should ask the user to do. Faster implementation gives those decisions more room. It does not make them unnecessary.

Source: Sayer’s tool history, as reported by Anything.

A second telling, from the same company

Anything has also published a testimonial attributed to William, identified as building Takeaways: “I was able to go from idea to App Store in 2 months!” That supports the duration in the customer story. Both accounts come through Anything; they are company-published evidence rather than two independent investigations.

“I was able to go from idea to App Store in 2 months!”

WILLIAM · BUILDING TAKEAWAYS
Published by Anything

The distinction helps keep the number honest. The published material does not supply a development log, hours worked, total cost or a breakdown of time spent testing and submitting. It gives a reported journey with an endpoint. Treating it as an average would require a collection of comparable projects, including the ones that stalled.

For planning, the right next move is to write down what makes your project comparable: scope, familiarity with the tools, time available and the standard a first release must meet. A customer example becomes more useful as those assumptions become visible. Otherwise, the attractive number simply travels from somebody else’s story into your deadline.

Source: Anything’s published William testimonial.

The work between preview and publication

Anything’s current mobile documentation separates building, phone previews through Expo Go, beta testing through TestFlight, and App Store publication. It also points builders towards testing native capabilities on a real device. A browser preview cannot settle every question about how a phone app behaves.

The current submission guide describes further work: an active Apple developer account, app information, screenshots, privacy details and the submission process in App Store Connect. Anything’s own review check can flag common problems before submission. Apple’s review remains a separate step. These are the documented steps today; they do not establish exactly how Sayer’s 2025 submission proceeded.

The planning implication is straightforward. Set a milestone for a working core flow, another for testing it on the intended device, and another for a submission ready to review. Leave room to respond to what each stage reveals. Assigning every stage the same optimistic finish date merely conceals the work.

This is why the two-month account is a stronger reference than a promise inferred from rapid code generation. It describes reaching a store, while a generation demo may finish with a preview. Neither tells another founder the date their particular app will be approved.

Source: Current mobile documentation · Submission requirements.

A launch is a moment; availability is ongoing

There is a present-tense wrinkle. On October 17, 2026, the linked Takeaways product site returned a Cloudflare origin DNS error. The two U.S. App Store listing URLs checked for this report returned 404 responses. A previously indexed Apple listing identifies William Sayer as the developer of “Takeaways - the details count,” supporting the product connection, but an indexed page cannot establish a download’s availability today.

Those checks do not prove the app is unavailable in every country. They do mean a current download recommendation would outrun the evidence. The June 2025 launch remains a company-reported historical claim; the product’s present distribution needs separate confirmation.

That final distinction belongs in the planning lesson, too. Publication is a milestone with a date. Keeping a product reachable is continuing work. Sayer’s reported two months gives a prospective builder something concrete to study: a small job, a first version, a journey to the store. Put those things in the plan before putting a launch date in the invitation.

Source: Previously indexed Apple product listing · Product site · U.S. listing 1 · U.S. listing 2.