AirSnap

Since we started our private beta, I tried to promote our product in several places, and here is the performance of each distribution channel so far.

I created a post here on IndieHackers and got very little attention. By the time of this post, I have 3 votes and 8 views.
https://www.indiehackers.com/post/just-launched-looking-for-beta-users-for-airsnap-mobile-session-replay-solution-933c3b4785

Shared on the product hunt forum and got only 3 upvotes without any responses.
https://www.producthunt.com/discussions/looking-for-beta-users-for-airsnap-mobile-session-replay-solution

I also tried the startup school forum and got no response either.
https://www.startupschool.org/posts/44766

I then moved over to Reddit and this is where we did pick up some traffic.

I first posted in the r/reactnative subreddit. The post got over 80 upvotes and a handful of comments. We also got more than a dozen people subscribed to our website updates.
https://www.reddit.com/r/reactnative/comments/rlwxye/we_built_an_app_to_help_you_reduce_debugging_from/

Shared the same post in the r/SideProject channel. The posts didn't do as well as the other subreddit, but we still got 16 upvotes and some comments.
https://www.reddit.com/r/SideProject/comments/rlxg9a/we_built_an_app_to_help_you_visualize_your_entire/

My assumption is Reddit probably has more active users compared to the other distribution channel and given that our product targets specifically mobile engineers, the React Native channel reacted more positively to it.

We completed our MVP and officially kicked off our private beta.

The primary goal of the private beta is to get feedback from our users to help us further improve and iterate the product. At the moment, we have a long list of roadmap items to get to, and we're hoping to leverage the private beta to help us better prioritize the next steps.

For every single person/team that is interested in our private beta, I try to get on a call with them in order for me to better understand their needs. I have done a couple of calls already and have a few more scheduled. In addition, I'm also trying to get more beta testers in the pipeline. My goal is to have 10 beta users by end of Jan.

My cofounder built a rough replay that was able to simulate the event replay in his local machine. The POC basically consisted of capturing the events locally, playing a video, and rendering the session replay with the data we captured from the mobile app.

After speaking with some users and received some feedback, there was not enough pain-point around the problem we were trying to solve, and we could not figure out a great use case to solve the problem we initially set out to solve. Therefore, after some careful consideration, we decided to pivot and also updated our landing page.

The reason why we decided to pivot is that this product solves a big problem we run into during mobile app development. Whenever a user reports a bug, our team usually goes into logging solutions such as Datadog, Sentry, Splunk, and event tracking analytics solutions such as Mixpanel to understand exactly what the user did which led to an error. This process requires jumping back and forth between multiple different products, trying to stitch the different pieces in order to connect the dots.

AirSnap wants to consolidate session replay, bug reporting, and event analytics all into one single solution to help expedite this process.

New landing page can be found here: https://www.airsnap.io/

We just completed our landing page here: https://www.airsnap.io/.

While the product is still being worked on, we want to start collecting some early interests and ideally get some feedback from people. I have shared the landing page on my social media and I will be spending time next week to try to re-iterate our landing page based on the feedback we receive.

I'm currently working as a product manager at a tech company and I always find myself taking tons of screenshots of our app to create documentations. The problem is the screenshots can potentially become outdated pretty soon given how fast things change. So I would end up not just taking screenshots of an entirely new feature/page, but I would also have to capture screenshots for minor changes to keep the documentation up to date.

In addition to that, I see our team is always using screenshots to communicate updates because it's much easier for people to visualize something than simply talking through words. So instead of asking the team to take screenshots whenever a change has been made, why not come up with some sort of automation that could streamline this process and reduce the manual effort.

This will also be beneficial in the remote-first environment where asynchronous communication is encouraged. Instead of waiting for the build to complete and manually take the screenshot, the engineer can just kick off the build and close his laptop. AirSnap will be responsible for sharing and capturing the screenshot of the updates and automatically publish it.