Day 41 - Ready to re-research
Finally time to start reaching out to potential users again tomorrow. Love the transition from Webflow to Softr & Adalo in here, so happy with how this will look on the users' end:
Day 40 - Landing on a page..
Working on the beginning of a design system in Webflow to re-use in the future. Lots of philosophical questions about how to structure..
Day 39 - Finding middle ground
Having a hard time keeping up the daily cadence as I'm moving into a new apartment, but managed to do a few things today:
- My favorite thing about visual development is being able to respond super quickly. This happened in the chat today:
- I dove into the Telegram API to automatically send people's submissions to the chat 😃
This does confirm that the 'feedback loop' is more important than just the streak. Getting notified that someone else is making probably also reminds you and inspires you to keep making.
- I'm starting to build up a UI kit in Webflow, which I'll use for the landing pages:
Day 38 - Feedback & features
Discussed the progress so far with a few members of the group: all of their testimonials are really, really positive and they're all making more music.
Good sign. Some new things that we've discussed:
- Adding comments back into the app - We do all miss the social aspect of 'dropping' something and getting the hype of the group to back you up, so I'm going to
- Setting a specific timeslot to make music - I spoke with users about the moments they make music and what their most obvious 'competitor' is - the thing they do after a day's work instead of making music. Turns out, the time is there, but it often goes to other hobbies or commitments. I'm going to try and add a specific time to the intention to make things more tangible.
- "I want feedback on this" button - along with comments, a way to show the group you want feedback on a specific aspect of your upload; chords, melody, structure, etc. The cool thing about this? We'll build up a database of feedback :)
Day 37 - UI Kitting
Researched getting our UI kit in Webflow today - will definitely help building the necessary pages for this & future projects 🏗
Day 36 - Consistency
Finished the Softr prototype today:
Looks like it'll be consistent with what I'll be doing on Webflow & Adalo 😃
Day 35 - Taking shape
Softr is just insane. Built a prototype for Exercises in 2 minutes based on yesterday's Airtable base. Will touch up a bit and it's ready to go.
That means there's some more time to think about how to share these ideas. Working on a simple landing page for both concepts, so I can add on mini products in the future:
Day 34 - The actual work
List of exercises is starting to build up nicely:
I'll probably build a simple Softr version just to get some early feedback from the people I reach out to, then build up the exercises as I go.
Day 33 - Ready for launch
Weekly update is over here:
Spend the past few days tweaking & fixing some bugs here and there. It'll be exciting to see people's experiences next week.
Day 30 - Let's go!
I've managed to get a rough first version out today, to test with the current group:
There are some features I had to postpone because I'm using these beta features (like notifications), but I figured it's about time to get something out. Always be a little bit ashamed of your V1s 😅
Thoughts on Bubble + Adalo so far:
- Having Bubble's advanced features makes a massive difference in what you can build - in my case, I wouldn't have been able to build a scheduling feature, or reset everyone's streaks every week.
- It's great for Adalo's performance to just keep these things on the backend.
- The connection to the Bubble data is a lot faster and less clunky than I'd expect.
- Assuming the Adalo app is on the App Store, Bubble can be a great "bridge" for generating sharelinks and making content public, then having people sign up on web and continue on mobile.
- Doing it this way definitely slows down the initial build: for example, every change in the data model has to be changed in the API setup, which introduces a few more steps. Not an issue if the app won't change a lot.
- You can't access nested data, which is a major point - for example, if I want to show a persons' profile picture with every post they make, I need to add that picture to the post to access it.
- You can set up an API call to grab a list of things, but to filter that list, you need to change the API call, instead of just filtering the list in Adalo. That's definitely an issue if you're displaying the same data in multiple ways. It's also a bit of a technical story to get it right.
- I have to wait for the external users beta to implement a few features, but that's just a matter of time.
Day 28 - Deeper into this stack..
My laptop's back!!! So had some great progress today on the app - found out a lot more specific ways to deal with Adalo + Bubble, writing a little guide for later on how this is all set up. It's fast enough, so that's a really good sign. Also set up a little roadmap to build features in a nice overview on the Notion page.
I ended up with implementing push notifications, but as always, I think I found an edge case
- I’m using Bubble for authentication & as a backend for my Adalo app
- I’m implementing an API call from Bubble to Adalo to schedule push messages
- To do so, I have to send an email address along to let Adalo identify which device to send to.
- However, I’m using Bubble as Auth, so it can’t find the user.
I played myself. The feature is still in beta, so pretty sure this will be fixed on the Adalo side soon.
Day 27 - Build mode on
Getting a feel for the onboarding on Adalo:
Day 26 - Building & tweaking..
Working through the Adalo + Bubble combination today and getting some feedback on the accountability part. Decided to remix this into ‘Groups’ as we had some awesome submissions today and I just get so excited from sharing these demo’s.
Excited to test the idea of having people create a new group from scratch using the app, instead of me inviting them into a mega-group.
Day 25 - Multi-playerish?
Something didn’t feel 100% right about the proto I’m building, so I decided to test two additions: having specific accountability partners & setting a goal. The current version just felt a little too isolated. This also opens up doors to sharing and creating more mini-communities; which i think would really help with promoting vulnerability.
I also think this will create a simple story people can tell each other: I’m challenging myself to do X weeks of music making, you can check my progress here.
Day 23 - Ready to build
Designed a simple prototype for V1 of the habit tracker today: Tomorrow the build starts ⚒
Prototype is over here
Day 22 - Content, Community & skill levels
Had some good inspiration today from other makers & one user who didn’t end up being very active. Turns out, lots of successful communities have a boatload of content - this makes a ton of sense, so I need to think about showing more value upfront. Spoke with a pro musician on the app & exercises I’m prepping, and looks like that’s headed in the right direction. As I thought, skill level / being able to collaborate with each other is quite important for the community part, so that needs a bigger audience to really be effective - thinking about starting to match people up at a certain point.
On a tech note, I saw someone use Softr and that’s a crazy fast way to build something on top of Airtable. I spy an Adalo - Airtable - Bubble - Softr hybrid before going into Webflow 👀
My biggest inspiration for the exercise side is https://coolors.co/ - I am in love with this. Press spacebar to generate & shuffle, keep something you like. So simple.
Day 21 - But first, the thing that actually has users.
Today I decided to work on the mobile app for the existing community members first. I will learn more from building out the exercise part and email list, but! This takes less time and has a higher success rate. So I’d rather get this rolling first. Working out all the exercises will take time, so that’s something I can nicely do after the app is there.
This also gives me the opportunity to talk about the exercises as a separate mini product with some potential members.
My biggest question here is whether the effect will stay the same when I ‘de-humanize’ the experience. Ironically, the focus of the app is less personal and community-focused than something like the chat we have currently.
So worked on the onboarding sequence today, focusing on just having people’s streaks visible & nothing else for now.
Day 19 - Splitting things up
Weekly update is over here:
Spent some time designing the upcoming two experiments today: Different audience, different platform, different ‘asks’, different levels of commitment, same core problem.
→ email list with weekly exercises Existing community → habit tracker app + integrated chat
Day 17 - Feedback tool or habit tracker?
Part of the fun in the group right now is listening to each others contributions - this is awesome, but also something that other tools solve as well, and i’m afraid it’s quite dependent on established personal connections between people. One inactive member reached out to give similar feedback, because he already has a support network / people to get feedback from. This made me curious about the habit tracker vs. community tradeoff, which I want to explore a bit further. I’m drawing out a way to merge them, by having the chat as an ‘optional’ addition above a really simple tracker. So basically, single-player habit tracker → challenge a friend/group with the platform if you want → integrate with a chat tool if you want. A single player habit tracker could already be a github-style activity tracker, or! I could rephrase it as a musical journal - something to look back on and enjoy the random progress. So possibly: musical journal → accountability partners → feedback and collabs. Start just solo, then share your stuff, then go deeper and actually work together.
Even smaller steps would be: exercises (to get over writers block) → musical journal → accountability partners → feedback and collabs
Exercises could be a cool tool to share as well 🤫
The chat is interesting in itself → i think i’ll focus on musical journal for people who the chat is a bit too committed & focus on exercises as a ‘launch’
Day 16 - Have I tried turning it on and off again?
My laptop broke down, so I’m juggling everything on my iPad at the moment - not ideal but hopefully I can design some things for the community tomorrow..
Day 15 - Linking up
Got the database to sync on people's weekly 'experiments' :)
Day 14 - A little big experiment
Did some cool things today - I know I'd love to send push notifications at some point, or make the community 'feel' mobile - that's why I just wanted to figure out early on whether I could use Adalo for mobile and Bubble for web and backend, keeping styles consistent.
It's also a good excuse for me to geek out on this - Adalo is beta testing their External users feature and just rolled out custom fonts, so... It looks like this works pretty well:
Day 12 - Barriers to entry + weekly update
Here's the rundown for the full week:
Over the weekend, I've worked on wireframing the easiest way to get going and see the value. Will build this out to see if this feels different than pitching a community to people - curious if more people would 'just try'.
I also almost finished a song this week, thanks to the exercise getting me back into the flow - that's a good sign 🙂
Day 10 - Contradicting myself
When designing, I love trying to design two completely opposite approaches just to explore the right balance. Here's how I feel about the possible 'entry points' into the community:
The cool thing is - 1 is something I can build quickly, the other one is a slow-burn that I've set in motion, so there's an opportunity to learn about both & find the right balance while playing around.
Will fill in these gaps with some ideas tomorrow ✌️
Day 9 - Where is everyone hanging out?
Within the current chat, we already notice the benefits of having an established project at the beginning of the week - I made some nice progress in just 30 minutes of music making yesterday because I had a clear project.
I dove into communities a little more and found a nice list of Discord communities where people are collaborating & sharing their music. Will lurk a bit and see if I can contribute. I'm starting to wonder whether I should position this as a community first, or simply as a tool to stay accountable. I like tools like wip.chat that are pretty low-key in their messaging, but if you want you can go a lot deeper.
In the ideal situation, people won't be forced to 'switch' communities but MMM would be a layer on top just to stay accountable. Like almost single-player at first. So if I share this with people, it doesn't feel like a big step to try it out for a while.
And it's important to try it out for a while before seeing the results - which will be a tough sell. But joining a community and getting to know people is a bit of a commitment.
Maybe I should simplify the concept a LOT and just go with a simple field → what do you want to do this week? Then open up the feed. It'd be a nice design challenge as well to keep everything very low-investment at first. Maybe contrast it with a super high commitment.
Another thing to think about is where this thing will 'live' - What i like about the telegram chat is that it's very visible for people & easy to remember. Maybe go mobile-first to have push notifications right away..
Day 8 - Who needs a landing page when you have text?
Built a simple landing page in Super + Notion today to share when talking about the concept with people. I'm hoping / guessing the problem is strong enough to resonate with people using just copy:
Started with asking the people who replied to my post:
Let's see what happens -
Day 7 - If people had the problem, they would've been talking about it.
January 19, 2021
My reddit post yesterday had quite some good reactions which made me realize: there's solutions to the problem I'm solving ALL over the web. It's a good sign, as people are actually actively doing exercises to remove their writers' block (which is a solution I've been playing with):
I started gathering all people's tips, practices & tools in the Airtable base:
I can re-use a ton of these when designing exercises, but it also gives me a list of people who have been working on this problem before who I can reach out to. I brainstormed a bit about what I can add on top of these to make the community valuable, and it feels a bit like this:
And I couldn't help but wireframe a liiiittle bit to play with how to present solutions:
But! I'll still force myself to go fully text-based for a while. I think the strongest products are things you can just read out loud and get excited by because the problem they're solving is so well formulated. Tomorrow I will write up a Notion page and reach out to people from the Reddit threads, to see if I can get them to give me some feedback.
Day 6 - Keep it simple
January 18, 2021
I started the day by asking my little testing group what they wanted to focus on - I'm already super excited about what everyone is going to try:
I started logging people's experiments in an Airtable doc so I can use them for later inspiration.
To explore the problem a bit more, I complained on Reddit:
I hope I can get some inspiration here on the alternatives people currently use to solve this problem, and potentially find people who experience this problem.. I wasn't allowed to promote anything so I guess I'll follow up with the solution in private and slide into their DMs 🙃
Luckily there's more people who ask these questions, so I'll explore these answers as well:
Day 5 - I wish every MVP was this simple.
Jan 17, 2021
Day 4 - The smallest version.
Jan 16, 2021
While I research the issue, tomorrow I'll build the smallest version of the community I can possibly imagine:
- Purely text-based.
- Based in an existing messaging app (my eye's on Telegram)
- Me & a handful of friends.
- No automation (yet).
Beautiful UIs are awesome, but it's even more awesome to know why the UI is necessary in the first place. Of course this won't pass the mom test, but will definitely help me learn something for myself.
Day 3 - Frameworking vs. Working
Jan 15, 2021
I don’t like picking a side between ‘you should validate everything and interview yourself to death’ and ‘you should just start and see what happens’. So I’ll run two approaches in parallel:
#1 - Working - Just start something super minimal and see what happens naturally . (Shoutout Pieter Levels)
#2 - Frameworking - Spend some time thinking about the audience, problems & solutions and research them systematically. (Shoutout Ash Maurya, Clay Christensen)
I am too excited to start building, so this is a good time to force myself to think the problems through with a few frameworks 🙇♂️I love using the Lean Canvas & Jobs to be done theory.
For now, I landed on a main job to be done: Be proud of the music I made in my spare time.
With a bit more of a short-term job nested under that: Find a place for creating music in my life.
Mapped it out in the Figma file:
Day 2 - Where to begin?
Jan 14, 2021
Sometimes I feel like there’s two camps among people starting new ideas; the "just build, launch and see what happens" camp, and the "let’s fit everything into a startup validation framework" camp. I think there’s value to both approaches, and being able to build faster with low-code makes it possible to do a bit of both.
So I alternate a bit and find myself on a winding road between the camps:
I did start playing around with design a tiny bit. I feel like lots of ideas need a few nights’ sleep and need to crystallize a bit before they become better, so the sooner they are visual the sooner something feels real and you start to see the problems it will have.
Yesterday I defined the factors that I think drive the problem - I hope these will help me split up the solutions and test them separately, reducing the scope of my experiments.
By the end of this week, I hope to build an extremely simple prototype (pretotype?) that I can use by myself or share with a couple of people, just to test one solution. It’ll take time for me to build a habit as well, so the sooner I can get the single-player process running, the better.
Tomorrow I’ll use the Lean Canvas & the Jobs to be done framework to make more sense of the problems and guide me with some research. They won’t be a leading process in this case, but will serve as inspiration for questions to start figuring out.
Day 1 - What's the problem?
Jan 13, 2021
I spent some time today on writing out the problem I'm trying to solve. Splitting it up in this way will make it easier for me to scope an MVP.
Here's what I think my lack of music creation boils down to:
- Lack of habit & routine
- Getting into a creative state is difficult
- It's hard to be inspired at the right time
- Unrealistic expectations
I tend to focus on one subset of a problem at a time, just to see what happens to the idea when you cut out less important parts. The coming days I'll design a single-player MVP that I can use alone to start testing something tangible as I research the problem more thoroughly.
I also set up these page to start sharing my progress publicly ✌️