Web development · Malé, Maldives

Web development in the Maldives. Want a site like this one? Want to upgrade yours? Want a web app?

I’m Ismail Mohamed Fareed, a web developer in Malé. I build landing pages, business websites with a CMS and custom web applications. Never from a template.

Developer
Ismail Mohamed Fareed
Based
Malé, Maldives · works remote
Reply time
Usually same day

Who you’re actually talking to

The person who replies is the person who builds it.

No account manager, no sales layer, no brief lost on its way to a developer. Decisions take minutes instead of meetings, and your project is nobody’s second priority.

1
Point of contact
0
Templates used
0
Briefs handed on
project/<yours>/spec.md
1# before any code exists
2problem: "what is actually broken"
3users: "who has to live with it"
4scope: "what is in, what is out"
5data: "what the system remembers"
6flows: "what happens, in order"
7done: "how we know it works"
8 
9# only then: the stack
project/<yours>/stack.md
1# chosen after the spec, never before
2runtime: "what it has to run on"
3data: "a database, or a flat file"
4auth: "who gets in, and how"
5hosting: "what it costs every month"
6admin: "who edits it without calling me"
7exit: "how you leave, if you want to"
8 
9# boring, wherever boring is cheaper

Five kinds of work

Landing pages. Websites. Custom web applications. And two the Maldives asks for.

The line between them isn’t page count. It’s what the thing has to do.

01 / Landing page design

One page, one job.

Built around one purpose: a product, a campaign, an event. Simple in scope is not the same as cheap in execution.

ResponsiveCustom motionEnquiry formsSEO basics
02 / Business website development

Many pages, real content.

Business websites and directory sites for Maldivian companies: search, filtering, forms, and a CMS you can operate without calling me every week. Bilingual Dhivehi and English where you need it.

CMSSearch & filterDhivehi / RTLAPI integrations
03 / Custom web application development

When the site becomes a system.

Accounts, databases, role-based dashboards, payments, integrations. Less about presenting information, more about running an operation.

Auth & rolesDatabasesAdmin panelsPaymentsAutomation
04 / E-commerce website development

Selling online, in the Maldives.

Product catalogues, carts, local payment gateways and delivery that knows the difference between Malé, Hulhumalé and an island two ferries away.

PaymentsInventoryOrdersAtoll delivery
05 / Guesthouse & resort websites

Bookings that come direct.

Property websites and booking engine integration for guesthouses, dive centres and small resorts — built so you depend less on the OTAs.

Booking enginesFast galleriesMulti-language
  • Next.js
  • React
  • React Native
  • TypeScript
  • Tailwind CSS
  • Vite
  • Supabase
  • PostgreSQL
  • Firebase
  • Cloudflare
  • three.js

Priced on what it has to do, never on how many pages it has. What a website costs in the Maldives →

How the work gets made

I don’t start with a template.
I start with the problem.

Nothing over-engineered to sound impressive. Nothing under-engineered to save me a week.

01

Design is the product

Not decoration bolted on at the end. Structure and interaction are the functionality.

02

Motion with a reason

To show continuity and guide attention. Never because something could move.

03

It has to work properly

Fast, accessible, secure and tested as part of the build, not sold as an extra.

04

Different problems, different answers

No house style you get poured into. Your content and your users shape the result.

Recent project · 01

Go Construction · construction company website, Malé

Corporate website development for a Maldivian construction firm with nine years of built work.

Live in production
goconstructionmv.com
Go Construction website, built by LittleMan Dev in Malé: a dark, cinematic hero reading Building Landmarks with Excellence over a construction-site photograph, with a glass statistics panel.

Nine years of built work and no website that showed it. Now the projects carry the credibility and the interface stays out of their way.

  • ScopeSix pages and a full project portfolio.
  • DesignCinematic dark palette, editorial grid, full-bleed site photography.
  • MotionView transitions, so pages animate instead of blinking.
  • EngineeringHand-written, no framework. Built to be fast on Maldivian mobile connections.

Current project · 02

The Mosque Directory · a government web application

Ministry of Islamic Affairs and Endowments, Republic of Maldives.
Not public, and not finished. What you can open is a demo of the concept, running on sample data.

In progress · demo running
mosquedir.littlemandev.com
Mosque Directory web application for the Maldives Ministry of Islamic Affairs: a green gradient frame around a white card holding an interactive map of the Maldives with clustered mosque markers, a search bar and filter pills.

An official ministry platform, in development: every mosque in the country, searchable, on a map. Bilingual in Dhivehi and English, right-to-left throughout.

  • Demo todayMap, search, mosque records and a role-based admin module for ministry staff, running on sample data.
  • In buildA native app in React Native: prayer times, Qibla, Hijri calendar, offline access, issue reporting.
  • PlannedIntegration points for the ministry’s own systems: SQL Server, Microsoft 365 and eFaas.

Small by choice

I’m not alone.
I’m also not forty people.

A one-person web development practice in the Maldives that scales up deliberately — not a web design agency pretending to be one.

IFIsmail Mohamed FareedDesign, build, delivery, every project
+Designers & illustratorsBrought in by project
+Engineers I trustFor scale and specialism

What you get

  • One person who knows the whole system
  • Direct answers, not ticket numbers
  • Specialists added when the work needs them
  • Honest scope, including “you don’t need that”
  • The same person from first call to handover

What you don’t

  • Invented headcount
  • “Our team of experts”
  • Basic / Pro / Premium packages
  • Buzzwords standing in for decisions
  • A junior quietly assigned to your build

The honest version

Yes, AI writes a lot of the code.
No, that’s not the part that matters.

Code generation is the last step of the process, not the process.

Before: the actual work

Specs, requirements, architecture

A spec, a data model, an architecture. Written before anything is generated.

During: execution

AI executes the plan

A very fast pair of hands, working to a design that was already decided.

After: judgement

Review, reject, refine

Knowing what to reject is most of the skill. Nothing ships that I wouldn’t sign.

You can prompt an AI yourself. The difference is knowing what to ask for, what to throw away, and what finished means.

How a project runs

Six steps, in this order.

You don’t need a technical specification. Say what you want and who it’s for.

01

Get in touch

Email info@littlemandev.com, or call, WhatsApp or Telegram 7975770.

02

Describe it

What it does, who uses it, and your deadline.

03

Requirements & spec

I write the scope down, so we agree on the same thing.

04

Estimate & terms

A price for that scope, and a payment schedule.

05

Development

You see progress at the checkpoints, not at the end.

06

Payment & handover

Final payment, then delivery of everything we agreed.

The technology comes after the understanding, never before it.

Payment

Projects are divided into agreed checkpoints.

A deposit before development begins. The rest on milestones, or on completion.

Smaller projects
50 / 50
Deposit to start · balance on completion
Medium projects
40 / 40 / 20
Deposit · milestone · completion

Working software before the balance is due.

Larger applications
30–40 + milestones
Deposit · per milestone · final

Every payment tied to something delivered.

  • The schedule is fixed in the quotation before development begins, and does not move afterwards.
  • No 100% upfront, and no building for weeks on a promise. The risk is split, deliberately.
  • Delivery follows the agreed payment terms.

Delivery & ownership

What you own, and what it costs to run.

Ownership is settled in writing before the build, not argued about after it.

  • The domain can transfer to you on completion. If it stays on my card, that cost is billed to you.
  • Anything I keep running is quoted upfront as a monthly or annual figure.
  • Unpaid services get cancelled. Said plainly here so it is never a surprise later.
  • If you take it over, maintenance is mine only where we agreed it.
handover/checklist.txt
✓Live site, deployed
✓Source code & repository
✓Admin dashboard + accounts
✓Hosting & domain access
✓DNS configuration
✓Credentials, transferred securely
✓Documentation
·Third-party costs per agreement
·Maintenance only if agreed
handover/running-costs.txt
·hosting quoted before the build starts
·domain renewed once a year
·database only if it needs one
·apis metered, listed by name
·storage per gigabyte, if you store files
·upkeep only where it was agreed
  
·Every figure is in the quotation.
·Nothing recurring appears later as a surprise.

Let’s build it

Tell me what’s broken.
Or what should exist.

No spec, no wireframe, no right words needed. Describe the problem.

Ismail Mohamed Fareed Web developer · Malé, Maldives
+960 797 5770
info@littlemandev.com

Serving Malé, Hulhumalé, Vilimalé and the atolls, and working remote with clients outside the Maldives.

© 2026 Ismail Mohamed Fareed · Maldives Understand the problem first, then build the right thing.