Renting interactive screens for a stand in Riyadh or Bahrain is often the sensible choice. The risk is not the screen. It is the computer inside it that nobody has met. This is a story about a pending update, a palm on the glass, an Arabic heading that slid off the bottom of the screen and a coffee machine on the wrong circuit, with a checklist for anyone renting touchscreens for an event.
The message arrived on a Sunday afternoon with four photos and one question.
The photos showed interactive screens on wheeled stands, still in their plastic, lined up in a warehouse somewhere off the Eastern Ring Road. The question was short. “We’ve rented these for our conference stand. Can you make something for them in ten working days?”
It came from a marketing team in Riyadh. Their company makes clinical software, and they had a stand at a two-day medical conference in a hotel ballroom. The screens were booked. The graphics were at the printer. The stand builder had already sent the final drawing. What they didn’t have was anything to show on the screens apart from a PDF brochure and a product video.
Ten working days is tight, but it sits inside the shortest build window we work to, so we said yes. Then we asked for something the client hadn’t expected.
The model number. Of every screen.
The plastic wrap hides more than dust
A rented interactive screen is a computer you have never met. Someone else installed its operating system and chose its settings, and you can’t see what the last renter did to it. Two screens from the same rental company can look identical on a stand and behave like strangers.
The rental company was helpful and sent a spec sheet within the hour. Two of the four units ran Android. The other two, from a newer batch, ran Windows. From the front you could not tell them apart.
That changed the plan on day one. Instead of building for one system, we built a web application that runs locally on each screen and packaged it for both. We told the client early that the venue Wi-Fi was not part of the plan. If it worked on the day, fine. If it fell over, nothing on the stand would notice.
Then we asked if we could visit the warehouse.
Day four, in a warehouse with bad lighting
Our engineer spent a morning with the four screens. Some findings were small. One unit had a dead pixel near a corner. Another had its touch layer slightly off, so every tap landed about a finger’s width to the left.
Two findings were not small.
Both Windows units had system updates waiting. On an office PC that is a nuisance. On a stand it has a nasty sense of timing, because a machine switched off overnight and woken in the morning is precisely when an update likes to introduce itself. Say, at ten to eight on the first day of a conference.
On the Android units, pressing near the bottom edge pulled up the system navigation bar. A visitor leaning a palm on the glass could land on the home screen, among the rental company’s test apps and a weather widget showing a city in another country.
Neither problem is unusual, and both systems have proper ways to lock a device to one app. Android calls it lock task mode. Windows offers Assigned Access for single-app kiosks. The rented units had neither set up, because they were prepared for general use. With the rental company’s agreement, we locked each screen to our application, held the Windows updates until after the event, and wrote every change on a handover sheet so their technician would know what to undo.
The marketing lead asked whether all this was normal. It is. Rental hardware arrives ready for anyone. A stand needs it ready for one job.
The Arabic that looked right on a laptop
The content came together quickly. The team wanted a self-check quiz for clinicians that pointed each person to the right product module, plus a simple way to request a demo. The product video could play between visitors.
Arabic and English are standard in everything we build, so both languages were designed together from the first sketch. On our studio displays the Arabic looked perfect.
On the Android units it didn’t. The brand font in the design files was not installed on the rented devices, so the system quietly swapped in its own. The letters still joined properly, but the line heights changed, and one heading wrapped onto three lines and pushed the “Next” button below the edge of the portrait screen. A visitor would simply have been stuck.
The fix was to bundle the fonts inside the application instead of trusting whatever the device had installed. That took an hour. Spotting the problem took a morning with the real screen.
Late change, Tuesday night
Two days before the event, the rental company called. One of the Windows units had been double-booked. They could send a replacement, but it was a different model with a different resolution.
Calls like this are ordinary in event work. It is why we had insisted on a layout that scales instead of one drawn pixel-perfect for a single panel. The replacement reached the hotel the evening before setup. Our engineer loaded the application, set the lock, recalibrated the touch and checked every page in both languages. It took about forty minutes.
With a fixed-resolution design, that would have been a long night of redrawing, or a stand with three working screens and one playing the video on a loop.
Setup day and the coffee machine
The stand sat near the ballroom entrance, beside a coffee station. Good traffic. During setup our engineer traced the cables and found the four screens and the coffee machine fed from the same floor box.
Late in the morning the machine ran at full load and the screens flickered. Nothing went down, but warnings like that rarely come twice. We asked the hotel’s electrician to move the coffee station onto a separate circuit, and he did. We also set every screen to relaunch the application by itself after any power interruption and return to the welcome page. If power dropped in the middle of a quiz, the next visitor would see a clean start, not a frozen question.
Then there was the light. The ballroom had a skylight nobody had mentioned, and in the early afternoon a bright patch crept across two of the screens. Dark backgrounds in the design helped. We also turned one stand a few degrees. Not elegant. The glare left the glass.
The form that asked properly
The demo request form needed a second look. The first draft from the client’s side had a pre-ticked box agreeing to marketing contact.
We suggested losing the tick. Saudi Arabia’s Personal Data Protection Law treats consent seriously, and a clinician at a medical conference is the sort of person who notices a pre-ticked box. The final form had two clear, unticked choices in both languages: contact me about a demo, and send me product news. Each screen saved requests locally, and the client received the export after the event, so nothing depended on the hotel connection.
We are not lawyers, and we told the client to run the wording past their own compliance team. They did, and changed one sentence.
Show morning
Doors opened at eight. Our engineer was on the stand at half past six. Every screen was on its welcome page, locked, with no update prompts in sight. Under the counter sat a bag of spares, including a mini PC loaded with the same application in case a rented screen gave up completely.
The hotel Wi-Fi faded at about ten, when the main hall filled for the keynote. The registration desk outside had a difficult half hour. Our stand carried on.
The quiz did what the marketing team had hoped. Clinicians stopped, answered a few questions about how their department works, and got a short result pointing to the relevant module. The sales team used that result as their opening line. By the afternoon of day one, people were talking about the quiz far more than the screens.
At the end of day two, our engineer exported the demo requests, cleared the local data from every device, removed the lock settings and handed the four screens back to the rental technician with the change sheet. The rental company got their hardware back as it left, minus the plastic.
What the client said they would do differently
On the debrief call, the marketing lead said the screens had been the cheap part. The expensive part would have been discovering on show morning that they didn’t behave.
Next time, she said, they would book the content team before the hardware. We would like that too. Choosing screens together is easier than inheriting them. Inheriting is fine, though, as long as someone meets the hardware before the visitors do.
This story is a composite drawn from common situations with rented touchscreens at conferences and exhibitions, not a single client project.
Before you rent interactive screens for a stand
- Do you have the exact model and operating system of every unit, not just the screen size?
- Can your technology partner test the actual units before event day?
- Who will lock each screen to a single app, and who will undo it afterwards?
- How will pending system updates be handled through the event dates?
- Will the application run offline and store data on the device, with venue Wi-Fi treated as a bonus?
- Has someone checked the Arabic layout on the real screen, with fonts built into the app?
- If the rental company swaps a unit, will your layout cope with a different resolution?
- Which circuit feeds the screens, and what else is plugged into it?
- Are consent choices on your forms clear, separate and unticked, and has your compliance team read them?
- Who from your technology team will be on the stand before the doors open?
Already booked the screens?
Send us the model numbers and your event date. We will tell you plainly what can be built in the time you have. Interactive stand builds typically take four to six weeks, and simpler builds need a minimum of five to ten working days from approval and advance payment. Our team is on the ground in Saudi Arabia and Bahrain, bilingual Arabic and English is standard, and a member of FAIM commissions and stands by every installation we deliver.
Start the conversationWhatsApp us+973 3557 7062
Or email info@faimglobal.com.
Related reading: why event apps should work offline first, designing touchscreens for busy floors, the conference registration queue that reached the revolving door and lead capture architecture for exhibition stands.
Questions buyers ask
Is it better to rent interactive screens or buy them for an event?
For a one-off conference or exhibition, renting usually makes sense. What matters is that someone tests the exact rented units, locks them to your application and plans for a replacement model arriving at short notice.
Can you build content for screens we have already rented?
Yes. Send the model numbers and operating systems as early as you can. We build for the hardware and venue in front of us, and we prefer to test the actual units before event day.
What happens if the venue Wi-Fi fails?
Our builds are offline-first, with redundant inputs and automatic recovery. Content and form entries live on the device, so the stand keeps working when the network does not.
Will Arabic display correctly on rented screens?
Bilingual Arabic and English is standard in our work. We test Arabic layouts on the real screens and build the fonts into the application, so the device’s own fonts cannot change the layout.
How much notice do you need?
Interactive stand builds typically take four to six weeks. Simpler builds need a minimum of five to ten working days from approval and advance payment.
Do you work in Bahrain as well as Saudi Arabia?
Yes. Our team is on the ground in Saudi Arabia and Bahrain, and a member of FAIM commissions and stands by every installation we deliver.
Sources
- Android Developers: Lock task mode (locking a dedicated Android device to one app)
- Microsoft Learn: Assigned Access (single-app kiosk configuration in Windows)
- Al Tamimi & Company: An overview of Saudi Arabia’s Personal Data Protection Law (consent requirements)
Found this useful?







