The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
StayOps is a lightweight operations layer for small rental property portfolios.
Keep property details, utilities, policies, contacts, stays, and recurring work in one place, so the day-to-day is easier to hand off, manage, and keep straight.
You can try the StayOps demo here:
https://stayops-demo-xi.vercel.app/
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
A beautiful website can lose a surprising amount of its character on a phone.
Not because it’s broken.
The buttons work, the sections stack, and everything technically fits. But the rhythm feels flatter, the hierarchy becomes weaker, and the mobile version starts to feel like a leftover from the desktop.
I wanted to avoid that with Sirnik, TOSOO, and APVist.
Each project needed its own mobile edit: deciding what belonged first, what could be simplified, and which visual moments were worth protecting.
I brought a few of those screens together in this short reel.
Different brands and different visual systems, but the same goal:
The mobile version should feel designed - not adapted.
If you’re working on a website and want that same level of care across every screen, let’s talk!
Hey! I just shared a write-up on something I learned while rebuilding a product with AI agents:)
The main idea is pretty simple:
Don’t put all your product context in one giant agent file.
Keep the main file small, and put the real product knowledge inside structured docs that the AI can navigate when it needs them.
This has helped me a lot when working on a SaaS product with a lot of business logic!
Sharing the full breakdown here:
I'm offering consulting services to set this up! :)
The table-of-contents-in-the-main-file pattern is the key move here - it keeps the agent's default context small while still giving it a map to go fetch the architecture or naming-convention doc only when the task actually touches that domain.
A few recent projects that made it out of Figma and into the browser 👀
The transition from that portrait hero into the stacked device mockups is smooth, curious how much of the three.js layer is custom versus a library like R3F.