Now
Nagakiba / Developer from Oman
Salim Amir Salim Al-Marhoobi
I'm a software engineering student from Oman. I like building the kind of apps I wish I already had: tools that start messy, improve through real use, and slowly become something people can rely on. Right now I'm studying at University of Technology and Applied Sciences (UTAS) and spending a lot of my free time shipping mobile-first ideas.
Stack
I know and work with Flutter, Firebase, Cloudflare, and practical AI tools.
Approach
Build the rough version, use it honestly, then keep sharpening it.
About
A small corner of the internet for what I am making.
I learn best when there is a real product in front of me. That is why my projects are not just practice screens or clean demo apps. They are things I actually poke at, break, redesign, and keep improving until the rough edges start to disappear.
I care about the small product details too: the empty states, loading moments, copy, account flows, and the difference between something that only works and something that feels easy to keep using.
Projects
The projects taking most of my attention right now.
WayVibe
Location-aware music player
WayVibe started from a simple idea: music should feel tied to places, not only playlists. You can place music zones on a map, bring your own songs, and let the app change the mood when you move through real places.
Jadwaly
Study workspace
Jadwaly is the study app I wanted for my own courses: schedule, PDFs, notes, AI chat, timetable import, study tools, and course progress in one place. It is meant to make studying feel less scattered, especially when the week starts getting busy. Parts of the document experience use Syncfusion .
Current Focus
What I am trying to get better at right now.
Making apps feel less like prototypes
I care a lot about the difference between "it works" and "it feels right." A big part of my work is layout, motion, empty states, loading states, and fixing the awkward moments users notice immediately.
Making tools people can actually live with
The goal is not to add every feature possible. It is to keep the parts that make the product clearer, faster, and more useful when someone opens it during a normal day.
Keeping the feedback loop close
I use my own apps while I build them. That keeps the problems honest: if something is slow, confusing, or overbuilt, I feel it quickly and can make the next version simpler.
Contact