Islamic technical practice is not a product category.

Ask people to imagine “Muslim technology” and a familiar product shelf appears.

Qur’an apps.

Prayer-time apps.

Hijri calendars.

Islamic finance.

Halal marketplaces.

Muslim matchmaking.

All of those can be useful.

But if that becomes the boundary of Muslim technology, we have made a category error.

A Muslim can build a compiler.

A database engine.

An accounting package.

A warehouse-management system.

A robotics controller.

Accessibility software.

A medical device.

Agricultural sensors.

Developer infrastructure.

A scheduling tool.

A secure messaging protocol.

None of these products needs an Arabic interface, a crescent logo, a Qur’an quotation or a Muslim-only user base in order for the work behind it to matter.

The Islamic question can live somewhere deeper.

We are confusing three different things.

At minimum, we should distinguish:

Technology built for Muslims

The intended users or problem domain are explicitly Muslim.

Examples might include prayer scheduling, Islamic learning, mosque administration or tools designed around Islamic financial constraints.

Technology built by Muslims

The builders happen to be Muslim.

That fact alone does not tell us that the product is Islamic, ethical, well governed or even culturally connected to Muslim institutions.

Technical capacity located in Muslim-majority societies

A semiconductor plant, aerospace programme, AI institute or software industry may contribute enormously to technical capability without being an Islamic project at all.

These categories can overlap.

They should not be collapsed.

Otherwise “Muslim technology” becomes simultaneously too narrow and too vague.

What if the Islamic part is mostly invisible?

Imagine an accounting system.

No Qur’an quotations.

No prayer widget.

No Arabic calligraphy.

No “Islamic mode.”

What could still make the practice behind the build meaningfully shaped by Islamic commitments?

Perhaps the company refuses a predatory revenue model.

Perhaps its financing structure avoids mechanisms its founders consider impermissible.

Perhaps worker obligations are taken seriously.

Perhaps privacy is treated as an entrusted right rather than an obstacle to advertising.

Perhaps marketing avoids deception.

Perhaps dark patterns are forbidden.

Perhaps data collection is deliberately minimised.

Perhaps accessibility is funded even when it is not the most profitable feature.

Perhaps the company refuses clients or uses that violate its governing commitments.

Perhaps intellectual property is handled with explicit rules around attribution, licensing and stewardship.

Perhaps maintenance is treated as an obligation rather than abandoning users once acquisition targets are met.

None of that is visually Islamic.

That may be the point.

A technical ethic that only exists in branding is not much of an ethic.

“Halal” should not become a sticker.

There is a danger here too.

It would be very easy to turn “halal tech” into another certification aesthetic:

green logo;

Arabic geometric pattern;

values page;

done.

That would reproduce the same category problem.

The difficult questions live in the operating system of the institution:

Who owns the company?

How is it financed?

How are workers treated?

What data is collected?

What happens when the user leaves?

Who can inspect the model or decision process?

How are harms reported?

Who has authority to override growth targets?

What happens when a profitable customer wants something the institution considers unethical?

How are conflicts of interest disclosed?

How are vulnerable users protected?

How does the company behave when nobody is looking?

Those questions are harder than adding prayer times.

They are also much closer to governance.

Human-led AI belongs here.

The same distinction matters for AI.

An “Islamic AI” does not become Islamic because it quotes hadith.

A system can contain religious content while being badly governed.

Conversely, an AI tool with no religious content may still be designed around meaningful commitments to human authority, privacy, provenance, restraint, transparency and accountability.

This is why human-led AI matters as an architectural principle rather than branding.

Who sets the purpose?

Who can approve consequential actions?

Who can interrupt the system?

Who is responsible for errors?

What context is the model allowed to retrieve?

What remains private?

How are sources and contributions attributed?

What happens when automation conflicts with a human boundary?

These are not Muslim-only questions.

But a Muslim technical institution should have answers rooted in its own ethical commitments rather than importing every norm from whichever platform is dominant.

The boring backend counts.

The cultural imagination of technology overvalues what users can see.

But serious technical capability often lives in boring layers.

Identity systems.

Payment rails.

Databases.

Logistics.

Standards.

Developer tools.

Security libraries.

Scheduling.

Storage.

Accessibility infrastructure.

Research tooling.

Interoperability.

Maintenance.

Documentation.

These systems rarely become inspirational posters.

They are what other systems stand on.

A Muslim technical network that only funds visibly Islamic consumer apps will never become a serious technical ecosystem.

It will remain a niche software market.

The ambition should be larger.

Muslims should be able to build for Muslims.

Muslims should be able to build for everyone.

And Muslim-led institutions should be able to develop technical practice whose values remain intact even when the product itself contains no religious content at all.

The question is not what the interface looks like.

Remove every visibly Islamic feature from the software.

No Qur’an quotations.

No prayer times.

No hijri calendar.

No Arabic aesthetic.

No Muslim-specific user base.

Now ask:

What would still have to be true about how this thing was conceived, financed, built, sold, governed, maintained and used for us to recognise an Islamic practice behind the build?

That is a much harder question than “what Islamic apps should Muslims build?”

Good.

Harder questions are usually where institutions begin.

---

Editorial note

This article is a normative argument, not a fiqh ruling. It deliberately avoids declaring specific financing structures, products or technologies halal/haram.