00:00:01

Simone Torrey: Yeah, twice a week. Helps the focus. This meeting is being recorded.

00:00:11

Adam Rose: Hello.

00:00:15

Iván Lopez: Hey, James.

00:00:17

James Redenbaugh: Oh.

00:00:20

Simone Torrey: The voice. There he is. Oh, at least the beach.

00:00:27

Iván Lopez: Just the beach. Okay. I like that.

00:00:31

Adam Rose: With a pina colada. At his bathing suit.

00:00:35

Iván Lopez: I'll imagine that inside this bottle there's.

00:00:38

Adam Rose: There you go.

00:00:40

Iván Lopez: Just like playing. Yeah, Totally worrying.

00:00:49

Adam Rose: If you're doing something right.

00:00:51

James Redenbaugh: Is that the Gulf of America behind you?

00:00:57

Adam Rose: Too soon, man. Too soon.

00:01:04

Iván Lopez: Sometimes in down here, we don't care.

00:01:10

Adam Rose: Yeah, good for you.

00:01:12

Simone Torrey: Please keep doing it.

00:01:14

Iván Lopez: If I were closer to the border, maybe I'll. I'll worry much. Yeah, I'm trying to see where can I turn off my background effect.

00:01:27

Adam Rose: No, it's giving us hope. It's the only thing giving us hope.

00:01:31

James Redenbaugh: Yeah.

00:01:32

Iván Lopez: Oh, well, not that. You said it's giving me hope. To me too. I leave it at that.

00:01:38

Simone Torrey: All right.

00:01:40

James Redenbaugh: Awesome.

00:01:41

Roarke: Morning, guys.

00:01:42

Simone Torrey: See you all.

00:01:43

James Redenbaugh: Good morning. Yeah.

00:01:45

Simone Torrey: So good afternoon for you.

00:01:49

James Redenbaugh: That's right. So we've got the prototype working on. On webflow, like I mentioned on Slack, it's got some bugs, but those are easy to work out. Most of them, hopefully. It was tricky. It was a big learning curve for me to get it. To get it going. I think all of us tried. Yvonne tried, Rourke tried and finally got it going. And what's great about it now is like I wanted, it's working through webflow elements. So we're using webflow elements for the. For the messages, the text input, the buttons, everything. Anything we want to add to the interface can be an element. So that means it's really easy to style. It's really easy to edit the design and add new features. So that's great. And I did a few style improvements last night. We can have a look at that and talk about it.

00:03:05

James Redenbaugh: But Yvonne also has some. Some screens to share in figma and some more detailed mockups we can look at.

00:03:16

Adam Rose: Is this loud? Sorry, people are vacuuming. Can you guys hear this? No.

00:03:23

James Redenbaugh: Okay, fine.

00:03:24

Simone Torrey: No.

00:03:24

Adam Rose: Okay, good. I was just going to ask, did you use any kind of framework or library to deal with sort of the, you know, dealing with an API or how did you guys integrate it?

00:03:38

James Redenbaugh: I can show you. I can show you the code.

00:03:47

Iván Lopez: Better.

00:03:47

Adam Rose: Simone Torrey will love that.

00:03:51

Simone Torrey: I can type my tax return in the meanwhile.

00:03:53

Adam Rose: There you go.

00:03:55

Iván Lopez: Actually, I was curious. To be clear, I do not have like that extensive experience working with APIs. But as far as I know, the main thing was the endpoints. I mean, to hitting them right. And on my side, I wasn't able to get a clear response when I tried it on Postman. I was able to. I saw the code you had and in the prototype you made, but it was just a plain HTML and still have difficulties.

00:04:34

Adam Rose: Yeah, I can move. Sorry, go ahead.

00:04:39

Iván Lopez: I still have some difficulties. So I was mainly curious if there may be some specific requirements for us when we need to hit the API endpoint to get a clear response.

00:04:54

Adam Rose: I think James found it. It was the course thing. I forgot that I'd stepped in that too. And I worked around it by just the page I was hosting for my version was on the same domain, so cross origin stuff was a non issue. But I remembered that I stepped into that problem initially too and I was trying to use it from some other domain. I can't remember where I was trying to test it from. Anyways, I think it's working now. Yvonne. At least James got it working last night and I think we had to push a change on the server to allow requests to come from different origins. Staging or the Village Builder site.

00:05:40

James Redenbaugh: Yeah. So you can access the code we're using on the webflow site if you want to check it out and see what we're doing. There's no framework right now. It's just vanilla JavaScript and it's. It's pretty simple and I think we can build on this to do more.

00:06:09

Adam Rose: I'll take a look.

00:06:10

James Redenbaugh: Yeah. So, yeah, you've. Adam, you've poked around with the prototype. You shared some thoughts on. On Slack already. And just to respond to your. Your comment, it is pulling every. I think it's less than a second, which would enable it to be open in multiple browsers. I don't know if that's necessary. I don't know if. If it significantly increases your. Your server load to do that.

00:06:55

Adam Rose: Not initially, that's for sure. You know, all the users that we have, hundreds of thousands. Yeah, so it's more. It's actually more like when you're developing, it's like, you know, things are scrolling off, you know, it's more that kind of thing that, you know, it's. But yeah, I'm not. When it does just to get of the last number of messages, it's just retrieving it from memory. So it's like super fast. So it's not like it's, you know, hitting a database or doing anything. So, you know, I'm not worried about the load right now. I think, you know, I think it's not something we like how we'd want to ultimately go to production like at scale, but like If. If that's a. I'm not sure we need to even worry about that scenario.

00:07:38

Adam Rose: Like someone in two different browser windows and, you know, does it need to stay in sync? You know, it's certainly not that vanilla use case, but I'm sure some, you know, like, particular user will do it. Yeah, I. For now, I don't think we need to worry about it right now, like as a thing we need to solve for. So it's probably better to just not do that and then we can figure out if and when we need to handle it or at least we can slow it down, you know, something like that.

00:08:24

James Redenbaugh: Any other comments you want to make on the prototype requests?

00:08:33

Adam Rose: No, no. I mean, I think it was just a basic, you know, like get something talking. So it's great. We got a starting point and I think we'll just add in the. The other components that we've talked about. Yeah. Did Simone Torrey get to see it? I don't know if you took a look at it.

00:08:50

James Redenbaugh: Have. Have you. Simone Torrey?

00:08:54

Simone Torrey: Yeah, I'm here. You can talk. You can address me directly. Miss.

00:08:58

Adam Rose: Yeah, hi, Simone Torrey.

00:09:01

James Redenbaugh: Did she.

00:09:03

Adam Rose: Can you tell us whether Simone Torrey looked at it?

00:09:10

Simone Torrey: Great. So now it's all on us getting the. The only thing I find weird is that the navigation of our site is there as well. But yeah, the really only thing is the connect button. That really throws me off for some reason.

00:09:36

James Redenbaugh: Yeah. Maybe we want to use a different visual language for these buttons.

00:09:41

Simone Torrey: Mm.

00:09:43

Adam Rose: I'm just wondering do we want to.

00:09:44

Simone Torrey: But it has to be, right.

00:09:48

Roarke: It might not need to be on the same type of navigation page. Maybe own interface.

00:09:55

Adam Rose: Oh, I didn't see here.

00:09:57

Roarke: Oh, I thought I said hi earlier, but I wasn't sure.

00:10:01

Iván Lopez: I got thrown off too Voice of Roark.

00:10:04

James Redenbaugh: I was like, hello.

00:10:09

Roarke: Yeah, the modes. We're not quite yet seeing the different modes. At least I'm not sure we are. Like whether or not if Alex is giving advice or if Alex is listening how we're doing that. I don't what you guys have thought about in that way.

00:10:32

Adam Rose: So I think what we said was we're just going to have a suggest button and. And it would be a dropdown. If you look at the page that I actually added it to, the page that is hosted at the base URL on staging and it's just a dropdown with some pre canned text. So it's like suggest some next steps. Suggest. You know, I don't know, I can't remember. But we can just fill in some sort of pre canned options. I Think they were. I took two right from Rosebud or something.

00:11:07

Simone Torrey: Yeah. So what we settled on last time, I think, was that weren't gonna. Or on a. Did we talk about it on Slack? Where did we talk about it? That weren't gonna have different modes, but were gonna do it like in. Oh, yeah, that was on the last call. A little bit like Rosebud does it. When you want suggestions, you. You just basically prompt it. It's like.

00:11:37

Roarke: Okay, just through the way of speaking.

00:11:41

Adam Rose: Yeah.

00:11:43

Roarke: Alex will prompt it.

00:11:45

Adam Rose: Yeah, yeah. So see here we just said get suggestions and all it literally does is takes the text from that box and injects it into the chat. So we don't want it to feel like two different people.

00:11:56

Roarke: Oh, yeah, No, I wasn't suggesting two different people at all. And I know that were worried about that perception of having to mod or talk with two different concepts. I remember that clearly. I just wasn't sure about how were talking about actually suggesting or prompting or creating that. I had put up some mockups at one point, but nobody gave me a thumbs up or any kind of identification if it had been seen.

00:12:24

Adam Rose: No, I thought I responded in there and let me. Yeah. I find I miss threads in Slack a lot because they're not. They don't jump out at me. But. Yeah, so any. I think that's what we decided we would want to do with that. I think, you know, we'll need to finalize what text and whatnot. And then on the back end, I think I'm just keying off those exact phrases and writing it to the other agent. But we'll need to get better than that over time. Like if they asked for us, you know, some suggestions just in a natural flow of text, we're going to need to, you know, detect that as well and make sure we handle it properly.

00:13:11

Roarke: Awesome. Go for it, Simone Torrey.

00:13:15

Simone Torrey: No, no, I was just.

00:13:18

Adam Rose: I was.

00:13:18

Simone Torrey: I was just laughing at James's question.

00:13:21

Iván Lopez: And yes.

00:13:24

Adam Rose: Some good advice.

00:13:26

Simone Torrey: Thanks, Alex.

00:13:27

Adam Rose: Help me evolve.

00:13:30

James Redenbaugh: It's great. It's really got me pinned.

00:13:33

Adam Rose: Yeah. Like, what are the top 10 questions Donald Trump could type into this thing?

00:13:43

James Redenbaugh: How to get Putin to like me even more.

00:13:49

Adam Rose: Send him flowers, dude.

00:13:54

James Redenbaugh: How to get Elon to finally respect me.

00:13:59

Iván Lopez: You can. You can do that.

00:14:05

James Redenbaugh: Cool. We can play with integrating that. Yvonne, do you want to share your screen and we can look at the screens that you have?

00:14:15

Iván Lopez: Sure.

00:14:30

James Redenbaugh: Here.

00:14:30

Iván Lopez: I think Simone Torrey already had a small peak into it.

00:14:35

Adam Rose: I did, too.

00:14:38

Iván Lopez: What do you guys think? But very quickly, I think we Can. Well, I hope and I think it won't be much problem. We can make. We can have one screen for the login and the sign up. We can only play with elements to only have one page and then interchange them. Whatever the user needs, we can have that in one screen. Then I was playing with some styles or ways of what we talked about where we. If we wanted to start a new conversation or we wanted to resume the previous one. So I was playing there with some elements, some effects that could look interesting that do not seem much like just a big square button. I wanted to make something a little bit more interesting. That's what I. In the first screen I had that triangle that.

00:15:35

Iván Lopez: Thanks Simone Torrey for pointing out that you like that. To be sure. I. I don't know what it is about the triangle that I like it too. Maybe that the colors, the thickness, like, I don't know, it resonates something with me. And for the last screen, triangle is.

00:15:54

Simone Torrey: Also about action for me. Like.

00:15:59

Iván Lopez: I don't know. I was even thinking if we could add like a small effect or the trial could be by spinning slowly. But that was just an idea. Maybe we can try it out when we start building this again to add a little bit more of motion and to not have the elements so static. And also because if we just had the. The without the some textures it just looks like too boring and I feel it's not so inviting. So that's why I was playing too with some of the wave details Moonji already made for us.

00:16:39

Adam Rose: Yeah.

00:16:40

Iván Lopez: And for the last one and what we talked from the previous conversation that right now it's not possible and we do not want to give the user this feeling that they are talking with different people or the agents that have a more synthesized and clear interface of the messages that the user is sending. In this case, I try to use the teal color, a darker style and like a more general color. Stick to the Alex brands where this is the responses we'll get from the API. Actually right now what were talking about, the thing we set up, I realized that I forgot to add the drop down or to play a little bit more with the options of the preset solutions. But yeah, these are like again like the starting points that we can have for the screens to keep polish them off.

00:17:45

Iván Lopez: For example, just as a small moment that I have. What are the fields that we would like to have the user to fill where they want to create an account? Again, I know we're like jumping a little bit into the future, but just to have the consideration on how will we play with those elements on the design and how will we have them define where the app is ready?

00:18:11

Simone Torrey: So one question for all of us. Do we need to have people's name and last name? Do we need to ask that?

00:18:22

Adam Rose: No, we don't have to. We just need their email address for authentication.

00:18:28

James Redenbaugh: Should we ask for the first names so the bot can.

00:18:33

Simone Torrey: Well, yeah. What. What I've often seen in the many apps I've signed up for to test them is they ask for how do you want to be called? So people have the freedom to use an alias as well because some people are very sensitive about their identity and with AI and especially.

00:18:56

James Redenbaugh: Yeah, Yep. Yeah. How cool would it be though?

00:19:03

Simone Torrey: Go ahead.

00:19:04

James Redenbaugh: If this ends up being the. The one that takes over the world.

00:19:12

Adam Rose: I like that. You're dreaming big, James.

00:19:16

Iván Lopez: We're not dreaming big. Why are we stepping out from the bed?

00:19:19

James Redenbaugh: Right.

00:19:21

Roarke: Force us in compassion.

00:19:23

James Redenbaugh: Yeah, you will love it in the relationship.

00:19:31

Adam Rose: Finally, we properly harmonized with AI.

00:19:35

James Redenbaugh: Sorry, you were saying, Simone Torrey.

00:19:39

Simone Torrey: The other question I had. Are we. Are we just doing Google or is there also an option like are we adding more? Is this just a placeholder or.

00:19:52

Iván Lopez: Yeah, this is just a placeholder. From what I said previously as right now I think we're. We do not have like established fields for the moment. Yeah, I just use like examples and reference from other login screens. For example there are some screens or other examples include like to register with your Apple account. But again this is something that we can add later. Mainly he is for. For filler. But to get to. To get that idea of how the screen might look like and just to come back a little bit about the name Adam. Actually I like the idea of having an alias. Again, I don't know if in some moment might be needed to have the name for the user or maybe just the first name.

00:20:41

Adam Rose: Yeah, I think we can either just say name or as Simone Torrey said, what would you like?

00:20:47

Simone Torrey: How do you want to be called?

00:20:48

Adam Rose: How do you want to be called? Or something like that, but it could just be one. One box. So if they could type two words if they want, but it can just be one box.

00:20:58

Simone Torrey: And then one other question I have. I didn't want to comment that because I didn't want to assume that you guys are not doing this, but are you running whatever you're designing through some kind of accessibility check, you know that it's visible like that it's well within standards for visually impaired people, etc?

00:21:24

James Redenbaugh: Yeah.

00:21:25

Iván Lopez: Question. Well, well, go on, James, you're the boss.

00:21:32

James Redenbaugh: Whatever we, whatever we push live, we definitely want to do that for. There's some tools we use once it's on webflow, while it's in figma. We just. We want to do our. Our best to adhere to best practices, which usually have to do with kind of font size and responsiveness. And contrast is really important. Yeah. And we've got good contrast ratios here, but these are good questions to ask and I think we should do a accessibility audit before the final versions.

00:22:20

Adam Rose: Cool.

00:22:22

Simone Torrey: I talked to the founder of a company who is launching in April. So soon they have like a whole AI based scanner for that. Yeah, that.

00:22:36

Iván Lopez: That's a.

00:22:40

Simone Torrey: One other question. Adam and I haven't discussed this, but is it possible to slide in somewhere? Kind of like a mindfulness pause screen, you know, like this other tool had like a breathe with me. Something that we could come up with that's ours. Like a little. Maybe it's even the three lines of, you know, of our website. Like just a visually beautiful with or without sound.

00:23:13

James Redenbaugh: Yeah. Maybe before this screen that's to the right of Yvonne's mouse right now, where you pick if you want to start a new conversation or resume a previous one, something could come up in that space. I'd also love to add a little motion to those forms. So. So it's like it feels alive. There's a little bit of a wave happening and it kind of implies a being. Like the negative space in the circle is this thing. And then in that we could have something come up, maybe some dots or that triangle in a way to show that something is coming. And then some text to guide you, like zoom into your breath, maybe have it sync with some. Something in the center that kind of grows. But if you want to think about that, sketch that out.

00:24:12

James Redenbaugh: We'd be happy to mock up a little demo of that or share some ideas of somebody else that's doing something similar.

00:24:23

Simone Torrey: Yeah, this Ash app is doing it. I was showing that last time, but it's basically just a circle and it says breathe with me. And then the circle expands for in breath and then out breath. And then the word in the middle is just breathe and it just goes in and out like a really calm, deep breath. Yeah, I don't want to copy that, but I really like the effect of it.

00:24:49

James Redenbaugh: Oh, and maybe there's like a skip button if. If somebody like just left and came back and they're like, hey, I just want to talk to Alex right now. I don't need to. I don't need To.

00:25:02

Iván Lopez: I need advice right now.

00:25:05

Adam Rose: Well, if it's. It. Yeah, I think it depends. Like, if it's only two or three seconds, you know, if it's just a quick thing, then yeah, I kind of like something like that actually, after this screen, just because it's sort of the transition from, okay, I logged in, I'm orienting now I'm starting the conversation. So it feels like when I click one of these, you know, and maybe the screen, maybe the text could fade away and the screen could just sort of become the breathing or something like that.

00:25:35

Roarke: Yeah, I was imagining, like it happening within the chat interface somewhere. You know, Alex might have listened to a com. You know, part of the conversation you said, and then said, hey, do you want to breathe? As one of the options. And then it gives you the ability to breathe right in it. Or maybe the. Maybe I don't have like an app, an icon, or any kind of branding in that screen yet, but maybe there's somehow Alex or some kind of thing could pulse at the pace of breath happen within that interface chat.

00:26:15

Simone Torrey: A pause button. A pause button. Like, so Adam's. Adam's wife as. As gifted. All of. So we're in a group, the four of us, doing some racial healing work for the last four years, and she has given all of us a pause button necklace. And the idea of the pause comes from Resma Manakim to like, just, you know, don't be always so rushing. That's so white supremacy. But like, take a pause.

00:26:48

James Redenbaugh: Wonderful.

00:26:51

Iván Lopez: This is very quick. It won't be so ugly as this one right now.

00:26:57

Simone Torrey: Make the skipper time.

00:27:00

Adam Rose: Yeah, we're not trying to encourage anyone to skip.

00:27:04

Simone Torrey: No, I'll call it, like, go back or something or move forward.

00:27:14

James Redenbaugh: Always just make it the same color as the background. So you really have to know it's there.

00:27:18

Simone Torrey: Yeah, I don't really want people to skip accessibility. This may be the best feature of the whole thing.

00:27:26

Adam Rose: Yeah.

00:27:27

James Redenbaugh: Cool.

00:27:29

Adam Rose: So maybe more just work. What you were mentioning made me think, something we are going to be doing down the road is integrating sort of micro practices. Right. So we might be saying, okay, we want you. You're gonna, you know, you're gonna text this friend that you had a conflict with. So you're nervous. So, you know, maybe we're like stepping you through it a little bit and we. That's where we're gonna need additional components of the app. It won't just be text. It'll be like, okay, we actually have some kind of workflow or something that you Know, you step them through a couple steps and so how that all works. It's definitely a later thing, but just what you were saying made me think of that and it just.

00:28:09

Adam Rose: More for your information, were absolutely thinking about things like that, like integrating practices into the Alex flow and we.

00:28:19

Simone Torrey: Those are actually ready.

00:28:22

Adam Rose: Yeah. They're not built yet.

00:28:26

Simone Torrey: They're waiting to be. They're waiting to be deployed. Yeah.

00:28:31

Adam Rose: Yeah. But how we sort of identify and suggest, you know, from the app, text, and then kind of kick that off. Like, kick that off. You know, if it's built separately, we'll have to think through a lot of that stuff at some point.

00:28:45

Simone Torrey: Yeah.

00:28:50

James Redenbaugh: Do you want us to go ahead and add the layer in here?

00:28:57

Adam Rose: You could add the screens. I'm going to get started. It looks like you're pretty close to being ready to actually put authentication on top, so I think we probably should get that implemented. I forget the name of it, but I found a. Like, I went down this rabbit hole and it's actually a whole rabbit hole. I guess that's why it's called a rabbit hole, because there's rabbits in there. Thanks.

00:29:25

Iván Lopez: What if it's a mole?

00:29:26

Adam Rose: Oh, it could be a mall. So there's a whole, like. Yeah, a mole hole. You're not making this easy on me, Simone Torrey. Come on. The whole, like, identity provider layer, right? Like, how do you manage user accounts? What if someone. You need to reset their password manually for them. What do you know, what kind of security policies? Like, there's a whole thing and a whole layer that sort of sits in the middle. And I don't think we want to build that. It can get really, a lot more complicated than it might seem on the surface from a simple login, but there's a whole bunch of stuff there. And so there was a service and I'm just not remembering the name of it, but I'll find it. And it looked like it would.

00:30:12

Adam Rose: It was cheap and it would do everything we would want to do. So it can manage accounts. But it's also. If we wanted to add other authentication methods like QR codes or email, one time email passcodes, or you want to verify through text. Like all the things that we deal with in terms of authenticating. We don't want to. We don't want to build all that stuff. Yeah.

00:30:38

James Redenbaugh: So easiest for us to set up would be member stack. Check that out. It's. It works natively with webflow really easily. We could pass the member ID to your app as a user ID and you Know, I could probably get it working within an hour.

00:31:06

Adam Rose: Okay, I'll take a look.

00:31:07

James Redenbaugh: Authentication and stuff like that. But the downside is it'd be tricky to keep using Member Stack when you get the full app build out. You'd probably need to migrate user data into something more robust and for what we're doing right now, it would work great. But if we're adding more dynamic and relational data, it might not suffice. The custom user fields are pretty limited there. We could also use wizd which is more complicated to set up but really robust also integrates, it's built for webflow and we could do more complex relational things with wizd and which, how is that spelled?

00:32:15

Adam Rose: That's not the one that Google bought, is it?

00:32:17

James Redenbaugh: I don't think so. W I z e d ed okay. And then there's OutSatta as well, which works like Member Stack but it's a little less customizable in terms of the login screen. But it also it has a built in CRM and email marketing features and things like that. As you're getting users that you want to keep in touch with. It handles that whole side of things for you too.

00:32:49

Adam Rose: Gotcha.

00:32:51

James Redenbaugh: Okay, so those are the options that I looked at and you might have a better.

00:32:58

Adam Rose: Yeah, I know, I was keeping the webflow in mind. Whatever I was looking at, you know they tend to build these things like you can build plugins so there's like a marketplace of, you know, to integrate to webflow or something like that but. Cool, I'll take a look. James, thanks.

00:33:15

Iván Lopez: Yeah, I think it will best to stick to with Wise. I hope I pronounce that correctly.

00:33:27

Adam Rose: Is that where are you using that already?

00:33:30

Iván Lopez: No, right now? No, no. But I think that would be the best because Outset and Member Stack, those are very good but those are the features they have built on with is to create a member site and correctly James, if I am wrong but by that same token I think there's not much live functionality with those tools to be able to call an API. So I think those tools will be mainly like to set up the login and the sign up. So I think it will be working much more many times with the specific endpoints with that API. I will think that WISE will be like the best option. We will need to see how to configure and make it easier to log in with webflow, the SRA with Google using Waste, that's just a little bit of throwing ideas in the air.

00:34:36

Iván Lopez: What do you think James? Yeah.

00:34:43

James Redenbaugh: Depends. Because since we're doing the API calls with custom code anyway, we don't need the Auth layer to. To be doing that. We just need that to generate the. The member ID that gets passed to the app. But as soon as we start getting into fuller backend logic and things like that.

00:35:10

Iván Lopez: Yeah.

00:35:12

James Redenbaugh: And as long as we're building it on. On webflow wised or. Or wizd is definitely made for that but the setup is more involved. We'd probably have to start using Xano as well. But then it really opens up a world of more possibilities.

00:35:35

Iván Lopez: I think that will relate. On what is Adam using for his backend too? Right. Is there something.

00:35:46

Adam Rose: The service that I was looking at is called Stytch. It's S T Y T Tch. Of course no one can spell it normally because the domain name would probably cost a million dollars. But S T Y T C H. What you don't want to do is implement like the actual oauth back and forth. There's some complexity in terms of token management and refreshing tokens and all this handshaking with Google or whoever. And so there's a whole bunch of stuff there that you really don't want to have to implement as like raw API calls. So I think you'd want to. Whatever we use, you'd want to make sure there's libraries that easily integrate with webflow that you can just say here's the username and password, log me in.

00:36:36

Adam Rose: And you don't want to get into the whole business of what magic happens under the covers to make that happen. So that I was just looking at the Auth thing but I haven't looked at this in weeks. So I'll take another look and see if. You know, I haven't even tried it, you know. But all of the kind of backend frame like I don't know what Xano might have something integrated out of the box too for this but thanks for that.

00:37:10

James Redenbaugh: Cool. I haven't heard of Stytch but I can look into this as well. So yeah, let's do our homework on that and see what's going to best.

00:37:23

Adam Rose: Cool. Yeah. Because there's also the whole backend side of it is like a portal to manage user accounts and everything like that. Right. Like that we need that customers don't see.

00:37:34

James Redenbaugh: Yep. Yep. And member stack out of the box. It easily handles things like change my password. Yeah, forgot my password. Or just send me a login link if I don't want yeah. To use a password, things like that. And you can do paid plans and stuff like that if you ever want to get into that. But yeah, see what's going to work for you and you should be able to figure it out.

00:38:08

Adam Rose: Great.

00:38:10

Simone Torrey: Do you want me to. Do you want me to think about this Breathe screen or do you want to play with it?

00:38:23

James Redenbaugh: Both. Yeah, I'd love. I'd love for you to do as much as you want to do on that. So if it's just. Just writing down a little brief, like, here's what I want it. Here's what I'm thinking, we can take that and run. Or if you want to do a little sketch or storyboard kind of thing, that'd be awesome.

00:38:55

Iván Lopez: Very quick. Sorry to interfere. I was just thinking how viable will be for you to have like a one input field that identifies either the email or the nickname. Or would you prefer to have both?

00:39:12

Adam Rose: We need both. You need the email because if you ever have to do stuff like resetting passwords or, you know, you need their actual email.

00:39:20

Iván Lopez: Well, yeah, but I was thinking in the screen of. For the login.

00:39:25

Adam Rose: Oh, yeah. You know, they could do either for the login, I think, but that. Oh, yeah, we're not going to guarantee that the alias is unique. I don't think, like two people could be called.

00:39:36

James Redenbaugh: Only be one Jeff.

00:39:38

Adam Rose: Right. Only one. That's the only one will make sure there's.

00:39:43

Simone Torrey: But you don't. You don't need that to be unique. Right. Because the account is with the email.

00:39:49

Adam Rose: Yeah, the email is.

00:39:51

Simone Torrey: And there's no. And there's no community where people could be confused.

00:39:58

Iván Lopez: Right? Oh, yeah, thanks for that.

00:40:05

James Redenbaugh: Okay, great. Well, I think next steps are pretty clear here.

00:40:10

Adam Rose: Yeah, Great progress.

00:40:12

James Redenbaugh: Yeah. Thank you, guys.

00:40:15

Adam Rose: Exciting.

00:40:15

James Redenbaugh: And yeah, we can be in touch on Slack. Should we set a next check in time?

00:40:25

Simone Torrey: Yeah, let's do that.

00:40:29

Iván Lopez: This is exciting.

00:40:32

Adam Rose: Oh, I know. What I wanted to ask one other question. It seems like you're designing very much with mobile in mind, even though it's sort of just on our website right now. That's what you're thinking, is that it would just still be a website, but it would be mobile, essentially. Mobile. Whatever you call it, mobile first or designed with mobile in mind and work well on mobile.

00:40:56

James Redenbaugh: Exactly.

00:40:59

Iván Lopez: Once we have mobile. Because sometimes it's actually the hardest thing to design. Because sometimes we can get so inspired that we get to create complex things on desktop and it's like, okay, now how do we fit all these things on a screen so small? Yeah. So Sometimes it's better to start up on mobile right now. The screens I think are fairly simple. So it won't be so difficult to visualize a version on a bigger screen. That's what I approach with mobile first in mind.

00:41:40

Adam Rose: Yeah. Yeah.

00:41:42

Iván Lopez: And a little bit about that from what you were saying, Simone Torrey, again, both of you feel free to add comments here on the Figma file. Any ideas or anything that could help us or you want to add on while we are working. Please go on. Feel free to give us a feedback whenever you feel like either here on. Like sometimes here is. It's much more helpful when you're thinking on very visual specific things. But yeah, the thing is feel free to add anything you feel like.

00:42:19

Adam Rose: Awesome.

00:42:20

Simone Torrey: And if I. If I want to play around with like actual visuals and I can always copy it onto my Figma board and then share that with you.

00:42:30

Iván Lopez: Sure. Miracle. Do you have editing credentials on this file?

00:42:38

Adam Rose: I don't think so. I think that meant you had to buy not free licenses and stuff.

00:42:44

Iván Lopez: Yeah, like I had an extra seat. Okay. You can do them. You can take whatever elements you would like. Edit them. Edit them. Sorry. On your own and then paste it. Paste it in this file and make a comment. It's like. Hey guys, this is what I was thinking. I have this idea. Anything.

00:43:08

James Redenbaugh: Oh, great.

00:43:09

Simone Torrey: So are we deciding that we're going with the first. With the first option here with the conversation, the one with the triangle or are you still playing around with it?

00:43:23

Iván Lopez: Well, to minus. That's my favorite screen. But that's my personal day and if you guys feel like this is the. That resonates the most, we can go with this. We could still play a little bit more but we will have this screen like. Or like I for. I don't know how to say it. Like the point from everything else will be part enough or to work from this screen over.

00:43:57

Simone Torrey: Right?

00:43:58

Adam Rose: Yeah, I'm good with it. I think it looks great.

00:44:02

Simone Torrey: Yeah, same. Especially remember prototype. It'll change, right?

00:44:08

Iván Lopez: Yeah, totally.

00:44:15

Simone Torrey: Don't let perfect be the enemy of good.

00:44:20

Roarke: Nice job, Ivan. Looks really good.

00:44:22

Simone Torrey: Yeah. Yeah.

00:44:25

Adam Rose: Sweet. Yeah, I'm out Monday, Tuesday next week. James. So if we. I don't know how. What are you thinking about a week or do you want to need a little more time?

00:44:36

James Redenbaugh: I think it'd be good to check in a week. I could do the same time on Wednesday.

00:44:44

Simone Torrey: Yeah.

00:44:45

Adam Rose: Yep, that works for us.

00:44:47

Simone Torrey: Yeah.

00:44:47

James Redenbaugh: Okay, great.

00:44:48

Iván Lopez: So very quick. I know that just. Simone Torrey, show us some screens from other apps. What were talking about. I don't know if I got confused. I thought that you sent some of those examples.

00:45:06

Adam Rose: Yeah, yeah.

00:45:08

Simone Torrey: In the figma board. Then my. In my FIGMA board.

00:45:13

Iván Lopez: Okay. If you could. Oh, yeah, it's not. If it's not problem. You could add those in. In the Slack channel.

00:45:26

Simone Torrey: James was on that board right now.

00:45:28

Iván Lopez: Yeah, Yeah.

00:45:30

James Redenbaugh: I just reposted a link right there. I'm also going to add it as.

00:45:35

Iván Lopez: A bookmark up top or in Slack. Okay.

00:45:39

Adam Rose: Okay.

00:45:40

Simone Torrey: It's on figma. But James posted the figma link in Slack.

00:45:45

Iván Lopez: Yeah, I can see it now.

00:45:51

James Redenbaugh: And I'm putting it in the top links in the bookmarks folder.

00:45:59

Simone Torrey: Yeah. See the. The black with the purple? Those are the guys who have the. Inhale. Exhale.

00:46:07

James Redenbaugh: It was already in there.

00:46:09

Simone Torrey: The screen.

00:46:10

Iván Lopez: I had to request for access to the file.

00:46:15

Simone Torrey: Yeah, approved. You. I didn't give them any credit card details, so we're not in any danger of getting charged.

00:46:29

Iván Lopez: Then suddenly the file will be no longer.

00:46:34

James Redenbaugh: Oh, okay, great. We have editing.

00:46:44

Iván Lopez: No, no, I think it won't be.

00:46:47

James Redenbaugh: Need. No. Oh, interesting.

00:46:55

Iván Lopez: I mean, if you want to add your credit card into Simone Torrey's account, I think.

00:46:59

Simone Torrey: I think it's free because there's a limited number of pages and you've probably exceeded the number of pages and I haven't. That's why it's free and.

00:47:11

James Redenbaugh: And projects. Yeah. But maybe you should start having clients start their own. There you go.

00:47:18

Simone Torrey: Yeah.

00:47:22

James Redenbaugh: Okay, guys, well, all right. See you next week. Have a great weekend. Weekend. Good to be with you.

00:47:27

Simone Torrey: Are you making. Are you making the meeting or shall I? I'm happy to.

00:47:32

James Redenbaugh: I already sent it.

00:47:33

Adam Rose: Oh, all right.

00:47:34

Simone Torrey: There you are. Perfect.

00:47:36

James Redenbaugh: Great.

00:47:37

Iván Lopez: All right, awesome. See you soon, guys. Bye, guys.

‍