52: Tuple Native App and Level Inbox Workflows

Ben is back from a productive retreat with his Tuple co-founders. It was deep concentration work that didn’t feel like a chore, but a feeling of joy. They experienced a milestone - scrapped the electron-based version of their app to work on a native functional prototype. There’s a ton more to do, but it basically works. The pieces are coming together.

Derrick understands the foundation required to pretty much get anything done with a new product. He is considering a future retreat, but wondering if the benefits are worth it to go off somewhere as a solo founder. Or, would it be more productive to be just sitting at his desk at home? The most critical item on his radar and one of the biggest unknowns he continues to battle is how the mechanics of Level’s Inbox will work. If it doesn’t function well, then the whole promise of the app breaks down.

Today’s Topics Include:

• Ben is trying to get to dog food ability - being able to pair using the app while actually working on the app
• Ben is using Basecamp and GitHub Issues to manage tasks that are still left to do
• Ben is still experiencing a steady stream of tweets, sharing, and sign ups for Tuple
• Derrick also has a steady stream of tweets and is up to 4,500 handle reservations
• Derrick is evaluating what paradigm he is mirroring when it comes to notifications and actionable to do items
  
• It can be counterintuitive but ultimately helpful to think about something so technical that it sends you back into a loop of higher level conceptual thinking
• Derrick’s making progress and at a decision point; trust his instincts and build something to be used, build a prototype, or build static mock-ups? Take a risk and set a date!

Links and resources:

Derrick Reimer Website
Derrick Reimer on Twitter
Ben Orenstein Website
Ben Orenstein on Twitter
Level
Derrick’s Manifesto
Tuple
Codetree
Basecamp
GitHub Issues
Drip