We recently announced our new pricing and plans, but how did we get those numbers? In this post we’ll break down MeetSpace’s scientific approach to pricing by looking at how to do a perceived value study and how to generate a Van Westendorp price sensitivity chart from the data using Google Sheets.
Today, MeetSpace is officially launched! Since the start of open beta in June we’ve squashed bugs and received lots of great feedback from our users. Based on our value study we did in August, we’ve put together a set of plan that cost exactly what the vast majority of users said MeetSpace was worth to them. For more information about out pricing, plans, and features, visit our pricing page.
This week, we’ve added the ability to unlock (and lock) rooms. When you unlock a room, anyone with the link can join, even if they don’t have a MeetSpace account. This makes it easy to introduce MeetSpace to your team at your next meeting, since you don’t have to get everyone to make an account right off the bat.
This week, we’ve added a live dashboard (and redesigned the dashboard to fit our new theme). The live dashboard shows you who’s currently in a room, and updates live as people join and leave.
When you’re writing a Go web application, there are a lot of ways you can test it. You can test each handler as a unit, or you can go for full blown acceptance tests with a framework like Agouti. In this post, we’ll look at how to test at the HTTP layer using the standard library
net/http with cookie support so you can test a full user interaction.
Screen sharing comes to MeetSpace! You can now share your screen or a window on Chrome and Firefox. Also, we got a new design, with a nice starfield background.
This week marks the beginning of the MeetSpace closed beta! So, there was a bit less development this week, but we did add Firefox support and a team settings page.
In our last post on pgcrypto, we covered using just PostgreSQL to hash and query passwords for authentication. Once a user is authenticated, you need to keep track of their session using cookies. In this post, we’ll look at how to generate and verify secure signed cookies with just PostgreSQL’s pgcrypto library.
This week we worked on the MeetSpace Rooms to improve the layout of participants, as well as introducing a new concept: Speaking vs Listening.
Users are central to any web application, and when you have users you usually need accounts, and when you have accounts you need password verification and cookies. Almost every web framework in any language has something for storing and comparing passwords and signing cookies to prevent tampering. In this post, we’ll explore how to do password hashing with just PostgreSQL’s pgcrypto.
This week we worked hard on the MeetSpace Dashboard. In this update we’ll look at a sneak peek of the dashboard plus explore some MeetSpace features like permanent rooms and teams. Lastly, we have a little beta update for you.
Structured logging is a modern take on log messages. Instead of plain text with a timestamp, structured logs have key value pairs. Sticking to common keys and formatted values, you can do some pretty powerful querying on your log data. In this post, we explore the basics of structured logging in Rails and Go with JSON, as well as the benefits of using a structure-aware logging system like current.sh.
This week our focus was on stressing out! We tried MeetSpace with 5 people, we tried a 90 minute call, and we even put MeetSpace on a plane.
In the past few weeks, MeetSpace has been getting off the ground with some research surveys and alpha work. Throughout all this there’s one clear message from teams that have online meetings:
When you host a meeting, it’s critically important to have the right people in the room. Seems obvious, right? But how exactly do you determine who those people should be? How do you tell someone they shouldn’t be there? How do you change participants over the course of recurring meetings? In this post, we’ll explore how to ensure you have the right people in your meeting.