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
MedMeet is the official mobile application for a major medical expo in Armenia. The platform provides attendees with comprehensive information about the event, including schedules, lectures, demonstrations, speakers, and venue details.
I independently handled the entire project from concept to deployment, including UI/UX design, React Native mobile development, Laravel/PHP backend development, database architecture, API implementation, testing, and production release. The result is a reliable and user-friendly application that helps participants navigate the event and stay informed throughout the expo.
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
Related posts
I've been testing a new app design workflow this weekend, and it feels fundamentally different from how I've worked for the past 20 years.
Normally my process looks something like:
Idea → Sketch → Figma → Prototype → Handoff → Build
This time I skipped most of it.
I wanted to see how far I could come without Figma using Codex. My first prompt was simply:
"Create a meal-planning app using the Build-iOS-App plugin."
It built a full app for me, but the first version was very generic, so I gave it a few design references and some visual guidelines and asked it to generate 3 different design mockups. Codex generated new design directions, I picked one and it applied the directly to the working prototype.
Mindblown. But then I asked it to create a logo inspired by another food app.
It did and even implemented it into the app directly together with an app icon.
No Figma involved.
As if this wasn't enough I was also testing a setup that exposes the iOS Simulator directly inside Codex using serve-sim.
That meant I could review the running app, click on areas I didn't like, leave comments such as "too much space here", and have Codex update the implementation directly.
No alt-tabbing between Xcode, simulator and Codex just to explain a simple detail.
Within about an hour I had a working prototype, visual design direction, branding, app icon, and multiple design iterations.
The quality wasn't perfect, but that's not what stood out to me.
What stood out was how little time I spent creating design artifacts.
Most of my time was spent reviewing, directing, and refining.
For early-stage product exploration, this felt less like designing screens and more like art directing a system.
I'm not convinced tools like Figma are going anywhere, but I do think workflows are changing much faster than most of us realize.
Has anyone else been experimenting with similar design-to-code workflows?
Good work
Just wrapped up my latest project ✨
A smart home energy monitoring app that tracks usage in real time, breaks down consumption by device, and surfaces AI-driven savings insights.
I'd appreciate feedback on the designs. Also, drop your thoughts in the comments.
The AI-driven savings insights screen is the most interesting part here. Surfacing actionable recommendations (not just raw data) is what makes smart home apps actually get used past week one.
I am mobile app and website developer
Challenges
View all
Trending
Claude
Claude has entered the design space. How are you using Claude Design?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
MagicPath
The canvas is infinite, and exploration is becoming the workflow. How are you using MagicPath?
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?