Day 41~53 of building a team communication app
Oh man I've definitely been too lazy posting on social media my progress but don't you fret I have been working on it a little at a time and here's some more progress!
#buildinpublic
Without animation, this would have been a less optimal code as the source of the spacing isn't as clear compared to coming from the parent `Row`.
Claude helped me solve it by moving the 12.dp away from the Row and into the modifier of the avatar and the send button themselves. The avatar got a `.padding(end = 12.dp)` while the send button got `.padding(start = 12.dp)`
spacedBy(12.dp) adds 12dp gaps between Row children. While it animates, its composable is still in the composition tree, so the gap persists. When the animation completes and the element is removed from composition, the 12dp gap snaps away instantly causing a jarring jump at the very end.
When no text was present, you only see the avatar with the text input. As soon as the user starts typing, the avatar disappears and the send button appears. Supposed to be a nice animation. Here was the problem.
Having a `Row` with the horizontal alignment parameter to put spacing between the items by 12.dp was my original code. There was an avatar on the left, a send button on the right, and a text input field in the middle.
Day 40 of building a team sports communication app.
Animations in Jetpack Compose is a lot harder than I thought, even with Claude's help. What seemed like such an easy thing turned out to be a bit more tricky to solve. Here's what I solved.
#buildinpublic #lesson
Day 39 of building SOOHO - team sports communication app.
Haven't been able to post updates as I was out of town to visit family but I have been still working on the app. Made some good progress, especially with the UI
#buildinpublic
Day 38 of building SOOHO - team sports communication app
Got to creating a Jira board to start tracking the bugs/todos for the MVP of the app. This board is gonna be completely full, but we go at it one at a time.
#buildinpublic
Day 37 of building SOOHO - team communication app
Seeing the logo that we decided on as a mock up in the figma design file is a surreal feeling as this just makes the thing I'm building more "real". The logo isn't even the final draft and it already looks amazing. Motivation!!
#buildinpublic
Thanks! Yeah that’s likely the cause. Time to let Claude find it and fix it lol
Day 36 of building a sports team communication app
Adding schedule events for admin feature is completed! There's some bugs like the calendar not updating when picking a date, but it's a start!
#buildinpublic
Day 35 of building a sports team communication app
Choosing the branding and logos are big for first impressions. Having difficulties deciding between some candidates. These are NOT AI generated and were hand crafted by our designer 😊. What's your favourite?
#buildinpublic
What do you like better? Trying to decide on a logo/brand for the sports communication app I am building
They all focus on sharp edges and a bold look for the brand. What’s your favourite?
Day 34 of building a team sports communication app
Populated the event detail screen with real data. The way things are going along I'm excited to start refining the UI with high fidelity designs and branding it!
#buildinpublic
Day 33 of building a sports team communication app
I was sick last week so had to put a pause on building. Came across GSD for Claude and wanted to try but with Pro plan I hit the limit so quick so maybe I'll just stick with prompting for now...
#buildinpublic
I did not know Android Studio's Gemini with the free version was so generous with its free tier. Going forwards I think I'm going to use the Gemini to ask it questions and brainstorm things and save Claude for more of the dirty work 😊
Day 32 of building a team sports communication app
A "bug" fix today where the timestamps were not translated into locale timezones. I've been using my Claude Code Pro plan for refactoring and cleanup purposes so this fix was done solo with the help of Gemini within Android Studio XD
#buildinpublic
Day 31 of buliding a team sports communication app.
Still managed to use Claude Code to solve the realtime chat update issue. Now we have live chat working! With how little time I have per day to work on this project at the moment, Claude Code has been a life saver.
#buildinpublic
Thanks bud!!
Haha those are just general communication tools. This is tailored specific for sports teams. It’s a TeamSnap and TeamLinkt alternatives.
So that not only will it be possible for me to fix the bug, but also easier for AI to read and fix and take less tokens to do it because it will be written better.
It can be difficult to sustain or scale since you rely soley on AI to build and fix everything for himself. But this is also a good opportunity for me to now go in and look at the code in a bit more detail rather than just glancing through and really understand and refactor the code.
This means I have to rely on Claude to fix the issue for me as well. I've asked it try and it failed twice. While I can go and do this many times, being on just the pro plan of Claude Code, I'd hit the limit in a heartbeat. This is the downside of using AI to build or "vibe code" products.
Day 30 of building a sports team communication app.
I think most build in public posts talk about progress. I'll talk about where I'm stuck. Real time database listening for supabase for my chat feature. Since I got Claude to do this, I didn't read the doc.
#buildinpublic
Day 29 of building a team sports communication app.
The basics of the chat ui is done, cool to see parts of it in action. Still not refreshing right away when I send a message, so hopefully can tackle that tomorrow. Excited to polish the UI when everything else is fully ready
#buildinpublic
Day 28 of building a sports team communication app.
Took the last couple days off/slow as my parents came into town to visit us and the kids. Managed to get a couple hours or so to continue working and start on the core feature of the app -- chat.
#buildinpublic
hahaha noooooo I wish I made it in 27 days. This is just the update for the 27th day. Not much progress in the last two since it's the holiday season. Follow along to see how many days it actually takes me LOL
Day 26/27 of building a sports team communication app
We’re winding down the last few days of 2025. I started posting more regularly on social media towards the end of the year, and I hope to maintain that momentum to get this app out to real users soon!
#buildinpublic
hahah yeah that explains a lot
