Show notes:
Links:
Saasler
Transcript:
*note - this is an unedited, automatically generated, transcript with only about 80% accuracy*
Ben
So I say we we just had a new customer signed up just like minutes ago and said that the reason they signed up was our podcast. So awesome. Good stuff. Good stuff. So pro tip for you says operators out there, put a little box and your on boarding, asking people how they heard about you or whatever. It's very, very informative.
Starr
Yeah, it does. And then do a podcast and wait episodes.
Ben
Those steps are optional. I really do like they're having like those, those uh onboarding introductions is what we call them. We have a channel in slack for them and having those show up periodically is like a little little endorphin rush. Like I love seeing those show up in our slack channel and you know, we also have a cancellations channel has the same thing with cancellation messages and that's not quite as fun. But thankfully we see if you are those messages that we do the onboarding messages, but I just, I really like having those things in slack. It's nice to see that throughout the day.
Starr
Yeah, definitely. So imagine this is gonna be a little bit of a shorter one because we just recorded um last week's podcast, like on monday in today's thursday. So I don't know if there's, there's not as much time that's passed to let um I don't know to let the hot takes regenerate themselves. Mhm
Ben
Right, well, I have a hot date for you and it's the grape, I guess most hot takes are great
Josh
what we're best at.
Ben
Uh so I'm working on an update to the Roku integration. So, you know, we haven't a clue add on and Uh we started to add on like, I don't know, back early, early days, it must have been like , or so. A long time ago. Well in , apparently Hiroki released an updated version of their API for partners like us and uh it has a new provisioning thing and you can actually call back to their API and get some information about like supervision to add on and stuff like that. Which is great. Uh We haven't ever really gotten around to changing our particular add on because it works just fine. So why bother?
Ben
But I've been looking at synchronizing the Heroku pricing with our current pricing because we've done a number of pricing variations since we launched the Heroku. And so now the two sets of pricing are pretty out of sync. So as I started to get into that I was like well you know well I'm here, how about I just you know update the A. P. I write classic classic rabbit hole. Right? And and and so I spent some time doing that and found you know some interesting quirks and so on about our integration and anyway it's all good like I got the work done and I did a pr and and josh and kevin like giving the thumbs up and I'm ready to deploy except
Ben
I have two questions for the Heroku people about about the migration because the migration you gotta be careful right? Because like the V one A P. I. Is not compatible with the V three Api And so you have to store different sets of data and the I. D. S in particular are different like they used to pass what they call a ready and now they pass an add on I. D. And you gotta you know handle the transition carefully or else someone you know maybe they can't add on the thing. Maybe they can't start being customer, maybe they can't remove the adult which would be a problem because you know or maybe they can't log in that would also again yeah prop trading right?
Josh
And so because they still get the emails
Ben
so so my questions for harajuku around this migration revolve around this idea and like handling sso and making sure that we can still provisions and provisions properly anyway. So I put two questions to them and support two days ago and that's my gripe because that's the holdup. That's the holdup I can't deploy it because I can't get answers to these questions apparently. So I'm just like oh okay I understand like people are busy and stuff but uh I would like an answer some time you know and there's no like there's no auto responder there's no we'll get back to you in X. Amount of time. No it's just like off into the void and I'm just waiting
Starr
did you maybe did you maybe use the legacy um support page Instead of the current ?
Ben
No no use the current one. Okay good question though. Good like that
Josh
this is just another example of like coding being the easy part. Uh huh.
Ben
Yeah and also a good example of like rd party integrations causing you know uh technical maintenance burden like like um oh for example like clubhouse that recently renamed themselves the shortcut. Right? And so we had to, you know, do a little bit of work there and renamed stuff inside of our app wasn't a whole lot of work but it was some work but you you add, you multiply that kind of work by the number of integrations you support and all of a sudden like this is ongoing maintenance work that doesn't, it's just you're just treading water trying to keep up with what everybody else in the world is doing. Right?
Josh
Yeah. And as new as new integration, you know, his new apps come onto the market and everyone wants to integrate with them, you just gradually expand until you, I mean you still have to support the old ones. Yeah, I think we're definitely getting to the point where every new little thing we add is like yeah, yeah, we're starting to feel it, we are starting to feel it. Yeah. And like the the depth of the integration is also I've noticed is like a big, big thing because like there's a few integrations that we like go a lot deeper with like get hub, you know, heroic. Who obviously is like a good example of that. We have a lot of issues with vera I've I've seen but who doesn't
Ben
um
Josh
but it does seem like the like I don't know, the more standardized something can be. Um and yeah, just I don't know when you're like integrating with a lots and lots of custom API's and stuff like that. They're going to switch it out on you at some point.
Josh
Yeah. Support. It
Ben
would be, it would be nice if there was like a happier plus plus, like a next level happier right? Where uh it just, it just abstracts away all these differences and you can just, you know, it's like a universal kind of thing and it's like, yeah, possibly be impossible. But
Josh
are almost like the pitch I get to the pitch there being almost like an LTs, like like an LTs contract for for integration API is like, you gotta, you gotta contract. This API isn't going to change for like years. Um and they'll just, you know, they'll do the and we'll do the internal migrations to keep the ap the same for you.
Ben
Yeah, there you go. That's that's an interesting idea. I wonder how that kind of service would cost.
Josh
I don't know, I know there's been a few um someone a micro, someone, a Microsoft had like a service that built like manage the integration side for you. Um was that Jonathan? Um Yeah, yeah, I don't know if that was like similar. I know it wasn't quite, that wasn't quite the idea, but like it was the idea that like,...