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
Fense is an AI-powered platform delivering smart recommendations for real estate and agriculture. By analyzing data and trends, it helps users make informed investment decisions, optimize yields, and identify high-value opportunities. Predictive insights, risk assessment, and actionable advice make Fense AI a practical solution for smarter, data-driven choices.
Appreciate that! 🙌, We put a lot of thought into making the onboarding and recommendation flows feel intuitive while keeping the product grounded in the real-world needs of real estate and agriculture. Glad the earthy palette resonated too 🌱
Absolutely. The recommendation engine is designed to get smarter as more user preferences, property data, location signals, and interaction patterns come in. Over time, that should allow FENSE to move from broad recommendations toward much more personalized land and real-estate...
Predictive/recommendation models like this usually live behind an API rather than on-device, curious how you're handling latency for the map view refreshes as new investment data streams in. Flutter's isolate model helps keep those recommendation recalculations off the UI thread if that's ever a bottleneck.
Yeah, for FENSE, the heavier recommendation logic lives server-side so we’re not tying the map experience to on-device model inference. The client mainly handles visualization and incremental updates as new data comes in. We’re also keeping the data pipeline event-driven so we...
Event-driven over polling makes sense there, keeps the map from re-rendering on every tick. Are you pushing those incremental updates over WebSockets/SSE, or is it more of a poll-and-diff pattern? That choice usually decides how much debouncing you need on the map redraw side.
Worth watching either way: once updates land as individual events, the map redraw cost usually comes from marker diffing rather than the transport itself. Batching events into a 200 to 300ms window and diffing by id before re-render tends to buy more than swapping transport does.
Yeah, that’s a good point. For FENSE, we’re treating the stream and the rendering layer separately, so batching/diffing is definitely something I’d prioritize before changing the transport layer. A short debounce window with ID-based diffs should keep the map responsive while...
Debounce plus ID-based diffing is the right fix, keeps render cost tied to what changed not event volume. Viewport culling stacks well on top of that, skips diff work entirely for markers outside visible bounds. Scales clean even if transport swaps later.
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
Challenges
View all
Related posts
🎰 6 POSTS AGO I ASKED: LUCK OR A PATTERN?
Well… apparently, a pattern.
Another Asol Design project was hand-picked by the Contra team.
Feature #7.
And this time it’s our AI Voice Notes App, another mobile product concept built around the same principle I keep pushing:
Great mobile design isn’t just about making screens look beautiful.
It’s about combining product thinking, user behavior, growth logic, and strong visual execution into one clear experience.
7 features later, I think the pattern is becoming pretty obvious. 👀
Thank you, Contra team, for noticing the work again.
More mobile product experiments, growth thinking, and probably a few more Contra features are coming. 👀
Next stop: #8?
#mobileappdesign #productdesign #uxdesign #uidesign #growthdesign #iosdesign #aidesign #figma #asol_design
Congrats 🎉
What should a platform for tokenized private equity look like?
Probably not like another traditional bank.
For ICME, the client wanted a visual direction that felt modern, disruptive, and native to a new kind of financial market.
The challenge was finding the balance: make the experience bold enough to feel different, while keeping a complex product understandable and credible.
I developed a digital-brutalist direction with retrofuturist touches - oversized typography, hard contrast, pixel textures, raw layouts, blue gradients, and controlled motion.
I worked with Arash Attar and the ICME team across the landing page and parts of the wider product interface. This video focuses specifically on the landing-page experience.
The goal was to:
— Explain tokenized private-company equity more clearly
— Create a memorable visual identity for the product
— Speak to both investors and founders
— Make financial technology feel ambitious rather than conventional
Would this visual direction make you want to explore the product - or should financial platforms feel more restrained?
This is amazing, man.
Good job!
