William Neill

Yeah, we built a really quick MVP in two weeks. We hired a guy from Central Europe to help us build that in native code. I think it was Objective-C at the time and Kotlin. And the MVP was purely just to get a sense of what's it like to save a link from a browser to an app and store it and then represent it, the UX around the saving process was really key.

Yeah, we built a really quick MVP in two weeks. We hired a guy from Central Europe to help us build that in native code. I think it was Objective-C at the time and Kotlin. And the MVP was purely just to get a sense of what's it like to save a link from a browser to an app and store it and then represent it, the UX around the saving process was really key.

So we wanted to make sure that we could achieve this idea of share from the browser and the sharing intent of that browsing session could be captured really well and brought into a mobile app that was there. So we built that, as I said, in two weeks. It worked really well. And it just gave us a sense of something in our hand that we could feel and go, yeah, this is a thing.

So we wanted to make sure that we could achieve this idea of share from the browser and the sharing intent of that browsing session could be captured really well and brought into a mobile app that was there. So we built that, as I said, in two weeks. It worked really well. And it just gave us a sense of something in our hand that we could feel and go, yeah, this is a thing.

So we wanted to make sure that we could achieve this idea of share from the browser and the sharing intent of that browsing session could be captured really well and brought into a mobile app that was there. So we built that, as I said, in two weeks. It worked really well. And it just gave us a sense of something in our hand that we could feel and go, yeah, this is a thing.

It's not massively novel at that point. There's other ways of like, you know, apps sharing to other apps and storing our data. But it gave us a sense of, yeah, we could feel how this would be if you found a product you liked and wanted to save it for later into a sort of a wishlisting tool and how fast that could be. Because that was probably the key thing is,

It's not massively novel at that point. There's other ways of like, you know, apps sharing to other apps and storing our data. But it gave us a sense of, yeah, we could feel how this would be if you found a product you liked and wanted to save it for later into a sort of a wishlisting tool and how fast that could be. Because that was probably the key thing is,

It's not massively novel at that point. There's other ways of like, you know, apps sharing to other apps and storing our data. But it gave us a sense of, yeah, we could feel how this would be if you found a product you liked and wanted to save it for later into a sort of a wishlisting tool and how fast that could be. Because that was probably the key thing is,

You're on a website and you're browsing. We don't want to get you out of that flow state. We want to keep you shopping and you want to stay shopping. So we don't want to interrupt. And so that process had to be as seamless as possible. So yeah, that was our MVP. From there, we looked at the process and the cost of building out an actual tool that would then give to the customers.

You're on a website and you're browsing. We don't want to get you out of that flow state. We want to keep you shopping and you want to stay shopping. So we don't want to interrupt. And so that process had to be as seamless as possible. So yeah, that was our MVP. From there, we looked at the process and the cost of building out an actual tool that would then give to the customers.

You're on a website and you're browsing. We don't want to get you out of that flow state. We want to keep you shopping and you want to stay shopping. So we don't want to interrupt. And so that process had to be as seamless as possible. So yeah, that was our MVP. From there, we looked at the process and the cost of building out an actual tool that would then give to the customers.

We decided that actually going the native route was going to be both costly and also fairly high maintenance for a tiny team to take on. So we took on Flutter at the time and decided we're going to build out with Flutter. That was interesting. So we'd shopped around with a bunch of agencies and asked, what are your thoughts on this?

We decided that actually going the native route was going to be both costly and also fairly high maintenance for a tiny team to take on. So we took on Flutter at the time and decided we're going to build out with Flutter. That was interesting. So we'd shopped around with a bunch of agencies and asked, what are your thoughts on this?

We decided that actually going the native route was going to be both costly and also fairly high maintenance for a tiny team to take on. So we took on Flutter at the time and decided we're going to build out with Flutter. That was interesting. So we'd shopped around with a bunch of agencies and asked, what are your thoughts on this?

And we'd raised a little bit of capital at that point to say, look, we're going to go and tackle this problem. And we were getting told that React was the only way to go. And yeah, we decided we'll fly in the face of convention and we'll take a stab at Flutter because we felt the community was growing pretty well and there were some opportunities.

And we'd raised a little bit of capital at that point to say, look, we're going to go and tackle this problem. And we were getting told that React was the only way to go. And yeah, we decided we'll fly in the face of convention and we'll take a stab at Flutter because we felt the community was growing pretty well and there were some opportunities.

And we'd raised a little bit of capital at that point to say, look, we're going to go and tackle this problem. And we were getting told that React was the only way to go. And yeah, we decided we'll fly in the face of convention and we'll take a stab at Flutter because we felt the community was growing pretty well and there were some opportunities.

So yeah, we dove into that and we're really actually happy we did. We felt like it's been a good decision. We've built out with, I guess, a lot of the Flutter tooling for the backend initially. Had to rewrite that quite often to make sure it stays fast and performant for all of the backend side of things. Yeah, we've crossed a lot of bridges to get to the point that we are now.

So yeah, we dove into that and we're really actually happy we did. We felt like it's been a good decision. We've built out with, I guess, a lot of the Flutter tooling for the backend initially. Had to rewrite that quite often to make sure it stays fast and performant for all of the backend side of things. Yeah, we've crossed a lot of bridges to get to the point that we are now.

So yeah, we dove into that and we're really actually happy we did. We felt like it's been a good decision. We've built out with, I guess, a lot of the Flutter tooling for the backend initially. Had to rewrite that quite often to make sure it stays fast and performant for all of the backend side of things. Yeah, we've crossed a lot of bridges to get to the point that we are now.