Urgent.News

What's breaking now, across thousands of outlets.

Tech

Dubai teen creates bilingual reading app to help children develop a love for books

Dubai: Like many children his age, Rakan would rather spend time on his tablet than pick up a book. His parents tried encouraging him to read, but it often took repeated reminders, and reading was never something he chose to do on his own. Watching her younger brother struggle to develop a reading habit gave 17-year-old Maya Lofty an idea. What if she could make reading just as engaging and…

Dubai teen creates bilingual reading app to help children develop a love for books

Dubai teenager Maya Lofty developed a bilingual Arabic-English reading app called IKRAA to help children develop a love for reading. Struggling to motivate her brother to read, Maya saw an opportunity to use technology to make the process more engaging and rewarding. IKRAA allows parents to set reading goals and children log their reading progress, earning credits toward rewards.

By making reading feel like an activity children voluntarily choose, Maya hopes the app will help children associate reading with achievement. The app is available on the website and aims to reach more families and schools. Maya believes reading offers benefits like imagination, confidence, comprehension, and understanding different perspectives.

Written by urgent.news from Gulf News's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at gulfnews.com →

More in Tech

Rig of Troy: A Suspicious Recovery Script Hidden Inside Roblox Toolbox Models

An investigation into suspicious R6 models, hidden GUIs, remote code loading, and a possible social engineering attack. 1. It Started With an Animation R6 models and animations in the Roblox Toolbox.

  • Suspicious script discovered in Roblox Toolbox models
  • Runtime.lua script found in Right Arm object of multiple models
  • Interface displayed instructions to execute external command

We Dropped Harbor for Large Images. A Traefik Default Was the Cause.

I stopped pushing large images to Harbor because the pushes kept failing. The cause was a default in Traefik, which I had adopted only because ingress-nginx was retired.

  • Large images (over 100 MB) failed to push due to Traefik's default readTimeout
  • 60-second readTimeout cut off parts of large image uploads, causing 504 errors
  • Adjusting Traefik entrypoint's readTimeout to 10 minutes resolved large image pushes

More from Wednesday 4 November →