about

About Skape

Hi! I'm Stephen. I've been in the software industry ~20 years and have worked as an engineer, PM and manager during that time worked at both big tech (Google and Microsoft) and small startups.

Skape started because I wanted a simple way to build apps for myself - as a software engineer, I know how to build infrastructure, but I found myself needing to repeat the same complicated infrastructure just to build simple apps. Also, in my career I built out the same pieces again and again - login, email notifications, sharing links. These are really similar between apps - why can't they be shared infrastructure too?

As someone who uses software, I found that when there were existing apps out there that solved my problem, I wasn't sure if they were selling my data or my location to advertisers. And if they disappeared tomorrow, would I be able to get my data out? And it seems crazy to pay $5/month for every single different app - most of that cost is because they each need to build their own infrastructure and have someone available 24/7 in case something breaks. The way we use software seems like it could be improve if we thought about it from first principles.

RemoteStorage and the larger community around 0data was interesting to me - they had servers that stored just the data for users, so they could own their data, rather than relying on app developers for storage. However, I found the nosql style of the database and the javascript API to be hard to work with. I also thought that pairing apps and data together was much more powerful - I wanted to be able to easily build apps and customize the apps that I used every day. This led to Mercato, an early concept that was based on remotestorage and had apps and data stored together, but I didn't spend much time trying to market it.

Then, coding agents grew powerful enough that you could just build apps by asking for them, and I decided it was time to build Skape.