Yesterday was about organization and polish — making sure ARVX not only looks good but also stays on track as it grows.
I set up a Jira board and broke my work into user stories and tasks. Having the roadmap is great, but this step made it actionable. Now I can see exactly what’s next instead of keeping it all in my head. It’s already making the project feel more structured.
I jumped back into Figma to keep refining the ARVX logo. I ran into a snag: figuring out how to flatten an effect so the design exports the right way. It’s a small detail, but details matter when you want your app to feel professional. Once I crack this, I’ll have a logo I can carry across the app and marketing.
To avoid hardcoding values, I set up custom theming for Tailwind — colors, fonts, and spacing. This way, ARVX has a consistent look and feel, and I can scale the design system as new screens and features come in. It’s a small upfront effort that’ll save a ton of time later.
I also read through Expo’s splash screen documentation. I found a Figma template guideline that lines up with Expo’s requirements, which is perfect because it means I can design the splash screen right in Figma and export it cleanly when I’m ready to implement.
Day two was about tightening up the workflow and setting the stage for smoother development. Between Jira tasks, Tailwind theming, and design exploration in Figma, ARVX feels like it’s moving from “idea” to “real product.”
Next up: I’ll continue to tackle the logo & icon design + work on getting a splash screen set up.
I’m a fullstack developer passionate about creating dynamic, performant web experiences. Whether it’s a sleek front-end interface or a robust back-end system, I can help bring your ideas to life. Send me a message and let’s get started!
