Ruby on Rails for a Dubai startup: where it still makes sense, and where it does not
Where Ruby on Rails still makes sense for a Dubai startup, UAE hiring realities, and when a founder should choose something else.
Read the articleMost problems in the website development process in Dubai are not technical. They are sequencing problems: content arriving after design, approvals waiting on someone who is travelling, a decision taken in week two that gets reopened in week nine. The work itself is well understood and the order it happens in is where the money goes.
This is a description of the website development process in Dubai as it actually runs, stage by stage, with notes on who has to be available, what you should have in your hands at each handover, and which stage reliably overruns.
Stage one of the website development process in Dubai: discovery
Discovery is where you establish what the site is for. Not the pages, the purpose: who it is addressed to, what you want them to do, and how you will know whether it worked.
On a small site this can be one meeting. On a larger one it involves looking at your current analytics, your enquiry sources, the questions your sales team answers repeatedly, and what competitors are doing that works.
What you should receive: a short written statement of the objective, an agreed page list, and a note of anything the site must integrate with. Three or four pages is plenty. If discovery produces a forty page document nobody reads, it was an exercise rather than a stage.
Where it goes wrong: agreeing a page list without agreeing what each page is for. A page list is not a brief, and the website development process in Dubai routinely proceeds on one because it feels like progress.
Who has to be available: whoever can decide. If the person with the final say is not in discovery, their opinions arrive during design review instead, which is the expensive place to hear them.
Stage two: content, which should start now and usually does not
Content is the stage of the website development process in Dubai that determines your launch date, and it is almost always treated as something to do later.
Content means the words on each page, the photographs, the product information, the staff biographies, the case studies and the legal pages. Somebody in your business has to produce or approve all of it, usually alongside their actual job.
Why starting late is so costly: design and build can proceed with placeholder text up to a point, and then they stop. A build that is finished except for content sits waiting, and the people who built it have moved to other work, so picking it up again a month later costs more than finishing it would have.
The practical approach: write the content for the five most important pages first, in a plain document, before design begins. Real copy changes design decisions. A heading that runs to twelve words, a product list with forty items, a biography with no photograph available: all of these affect the layout and all are better known early.
Arabic content deserves a specific decision. If the site will be bilingual, decide at this stage whether Arabic is a translation of the English or written separately, and who approves it. Retrofitting a second language into a finished build is more work than building for it from the start, because the layout has to work in both directions.
What you should receive: nothing from the supplier. This is your deliverable, and a supplier who does not say so clearly is setting up a conversation about delays that will be uncomfortable for both of you.
Stage three: design, and reviewing it usefully
Design work on most projects produces a few key page layouts rather than every page: a homepage, a main content page, a form page, and whatever is distinctive about your site.
Review the structure before the styling. The useful questions are whether the page leads a visitor towards the thing you want them to do, whether the important information is above the point where people stop scrolling, and whether the page works at phone width. Colour and typeface preferences are real but they are not what makes a page perform.
Ask to see it on a phone, early. Most visitors in this market arrive on a phone. A design approved on a laptop and squeezed into a narrow screen afterwards is how sites end up with a form nobody can reach.
Consolidate feedback into one response. Three stakeholders sending separate comments on different days produces contradictory instructions and a designer guessing at priority. One document, one round, with disagreements resolved internally first.
Accessibility costs less when designed in. Contrast, text size, focus states and sensible heading order cost nothing at design time and are tedious to retrofit. The published guidelines are the reference.
What you should receive: approved layouts for the key page types, at desktop and phone width, with a note of which states are included. Then stop changing them. Design changes during build are the second commonest cause of overrun in the website development process in Dubai, after content.
Stage four: build, and what to look at while it happens
Build is the stage of the website development process in Dubai you can see least of and worry about most. The useful thing is to ask for a staging link early and look at it regularly, rather than waiting for a finished reveal.
Ask what the site is built on and who can change it. A content system you can edit yourself, with a reasonable number of people trained on it, is worth more over five years than a slightly faster page that requires a developer for every text change.
Integrations are where estimates move. A payment gateway, a CRM, an accounting system or a booking tool each involve a third party whose behaviour nobody controls. If your project has integrations, expect the schedule risk to sit there rather than in the pages.
Watch the page weight. Large images and a long list of third party scripts are the usual causes of a slow site, and both accumulate during build without anyone deciding to make the site slow. The published metrics are the reference, and the right time to look is before launch rather than three months after.
Forms need to be tested by somebody who is not the developer. Submit them, from a phone, with a bad email address, with an Arabic name, with a UAE mobile number in the three formats people actually type. Form failures are the most expensive defect a business website can have because nobody reports them, enquiries just stop.
What you should receive: a staging link you can share internally, and a written list of what is complete and what is outstanding.
Stage five of the website development process in Dubai: launch
Launch in the website development process in Dubai is a checklist rather than an event, and most of it should be done before the day.
Before launch: every form tested and the recipient confirmed, analytics installed and recording, page titles and descriptions written rather than auto generated, a sitemap, redirects mapped from every old URL that is changing, and the site checked on a real phone on a mobile connection rather than office internet.
Redirects matter more than people expect. If you are replacing an existing site, every page that had any search visibility needs to point at its new equivalent. Skipping this is the single most common way a redesign loses traffic, and the loss shows up weeks later when it is harder to connect to the cause.
Domain and hosting should be in your name. Not the supplier’s. Confirm this before launch, because it is awkward to unpick afterwards and it is the thing that traps businesses whose supplier relationship later sours.
After launch: watch the enquiry volume for a fortnight. A site that launched correctly produces enquiries at a similar rate from day one. A quiet first week is a signal to check the forms rather than a sign that the market is slow.
What you should receive: administrator access to everything, a written note of what is hosted where under which account, the design source files, and a completed launch checklist. A website development process in Dubai that ends without those four items has not finished, whatever the invoice says.
Payment stages, and tying them to things you can inspect
Staged payment through the website development process in Dubai is normal and sensible. What matters is what each stage is tied to.
Dates are a poor trigger because a deliverable can be late for reasons on either side. Deliverables are a good trigger because both parties can look at the same thing and agree it exists.
A workable arrangement: a deposit to begin, a payment on approved design, a payment on a working build available on staging, and a final payment on the completed launch checklist and handover of access. Each one is inspectable.
Two things worth writing into the agreement regardless of how the payments are structured: who owns the work at the end, and what happens to the site if the relationship ends mid project. Both are straightforward to agree at the start and contentious to agree later.
Three local factors in the website development process in Dubai
Bilingual from the start or not at all. Arabic alongside English is common and it is a structural decision rather than a later addition, because the layout has to work read from either direction.
Hosting location is a question worth asking. Where the site is hosted affects how quickly it responds to visitors here, and for some businesses there are reasons to prefer particular arrangements. The regulatory authority publishes the relevant positions, and your own sector may have requirements of its own.
What the site may say about the business. Trade licence activity governs what you may advertise, and claims about services you are not licensed for are a problem regardless of how the site was built. If in doubt, confirm with the relevant authority rather than with a web supplier.
The short version
Start content on day one. Put the decision maker in discovery. Review design for structure before styling, and on a phone. Ask for a staging link early. Treat launch as a checklist. Tie payments to things you can inspect. Take ownership of the domain, the hosting and the files.
None of that is complicated and most overruns in the website development process in Dubai come from skipping one of them. If you want a view on a brief or a quote you have already received, send it over and we will tell you what looks missing.
Related reading on this site: the launch checklist in full, how to choose a website company, what to get at handover and building bilingual sites.
