Tag: Favoriot

The Day I Realised I Was Becoming a Human FAQ

There was a time when I actually felt proud every time someone asked me about Favoriot.

Each question felt like a small victory.

It meant people were noticing.
It meant the story was spreading.
It meant our work was reaching somewhere beyond our small team.

Someone would message me.

“What exactly is Favoriot?”
“Is it just a dashboard?”
“Can it connect to this device?”
“How is it different from AWS IoT or ThingsBoard?”
“Do you support AI?”
“Can students use it?”
“Is it for smart cities, or factories, or farms?”

And every time, I replied.

Patiently.

Sometimes through WhatsApp.
Sometimes through LinkedIn messages.
Sometimes through emails that arrived late at night.

Okay, Mazlan… this is good, I told myself.
It means people are interested.

So I kept answering.

Again.

And again.

And again.

Until one day, after probably the hundredth explanation, I suddenly paused.

I stared at my laptop.

Then I asked myself a question that hit me harder than I expected.

Wait… am I building a technology platform… or am I becoming a human FAQ?

That was the moment something clicked.

A small but powerful realisation.

This was not really about repeating answers.

It was about something deeper.

Energy.

Focus.

And scale.

Because if the story of Favoriot only lives inside my head, then every explanation will depend on me personally.

And that is not scalable.

That night, I realised something important.

When people keep asking the same question, it is not a problem.

It is a signal.

A signal that your story is not documented clearly enough.

A signal that your knowledge is trapped inside conversations.

A signal that your platform needs a voice that can speak even when you are asleep.

That was my first aha moment.

The Emotional Side of Repeating Yourself

Let me be honest.

There were moments when I felt tired.

Not angry.

Not irritated.

Just mentally drained.

Imagine explaining the same thing dozens of times.

Sometimes, even after giving a talk or presentation.

For example, after speaking at events like The Star Cybersecurity Summit, where I was invited to share thoughts about IoT systems, AI, and the future of connected technologies, people would still approach me afterwards and ask the exact same question.

“So… what exactly does Favoriot do?”

Part of me almost laughed.

Did I not just explain that on stage for half an hour?

Then another voice in my head replied.

Relax Mazlan. Every audience is new.

Every listener hears things differently.

Every person arrives with a different level of understanding.

Some are engineers.

Some are students.

Some are policymakers.

Some are just curious.

And none of them is wrong for asking.

That was my second realisation.

Repetition is not the enemy.

Confusion is.

If people keep asking the same question, it simply means the explanation has not reached them in a form they can digest.

And that responsibility sits on my shoulders.

The Turning Point

One evening, while replying to yet another email asking the familiar question, I suddenly stopped typing.

I leaned back in my chair.

Why am I answering this privately again?

Then another thought appeared.

Why not answer it publicly once… and let it help hundreds of people instead of one?

That thought changed everything.

Instead of seeing repeated questions as interruptions, I began seeing them as content ideas.

Every repeated question was actually a signal about what people wanted to understand.

If five people ask the same thing, it deserves an article.

If ten people misunderstand a feature, it deserves a tutorial.

If customers keep comparing Favoriot with other platforms, it deserves a structured explanation.

That was the moment I started writing more seriously on IoT World.

Not random thoughts.

Not marketing slogans.

But clear explanations.

What exactly is the Favoriot Insight Framework?

How Favoriot moves from raw data to meaningful decisions.

Why IoT is not just about dashboards.

How universities can build AIoT labs.

Why local councils struggle with smart city projects.

How system integrators can deploy IoT faster.

Each question became an article.

Each doubt became a story.

Each confusion became clarity.

And slowly, something magical happened.

Instead of repeating myself endlessly, I started sending links.

“You might want to read this article.”
“This explains the architecture clearly.”
“This post shows the use case.”

The conversation immediately became deeper.

People no longer start from zero.

They started with understanding.

Building Something Bigger Than Myself

But something else happened, too.

After publishing several articles, people began asking another question.

“Is there one place where we can read everything about Favoriot?”

I smiled when I heard that.

Alright, Mazlan… now the next step is obvious.

That was when the idea of a Favoriot Resources Page was born.

Not a marketing page.

Not a product brochure.

But a knowledge hub.

A place where people can explore the ecosystem properly.

A place where they can learn at their own pace.

On that page, anyone can now explore:

What Favoriot really is
Tutorials and technical guides
Real IoT project challenges
Case studies and architecture explanations
The Favoriot Insight Framework
AI and IoT integration concepts
Videos and learning materials

I wanted it to feel like a digital campus.

Because Favoriot is not just software.

It is an ecosystem.

And ecosystems require structure.

They require stories.

They require documentation.

Without those elements, people only see fragments.

With them, people see the full picture.

The Hidden Lesson for Founders

Many startups face this same challenge.

We assume people understand our product.

We assume our website is clear.

We assume our explanation is good enough.

Most of the time, it is not.

People are busy.

They skim.

They scan.

They make assumptions.

And sometimes those assumptions are completely wrong.

So when people keep asking the same question, the worst reaction is frustration.

The better reaction is curiosity.

Ask yourself:

Why is this still confusing?

Which part of my explanation is missing?

How can I make this easier to understand?

Repeated questions are feedback.

Free feedback.

Valuable feedback.

And if you listen carefully, they tell you exactly what your audience needs.

When the Story Finally Clicked

After writing consistently and building the Resource page, I noticed something interesting.

My explanations became sharper.

Writing forces you to think clearly.

When you write publicly, your ideas become structured.

And suddenly the narrative becomes easier to communicate.

People begin to see the bigger picture.

They understand that Favoriot is not just a tool.

It is a framework.

It is an ecosystem.

It is a learning platform.

It is an AIoT foundation.

Without structure, that sounds confusing.

With structure, it becomes powerful.

The Resource page helped me connect the dots.

From devices to cloud ingestion.

From data streams to analytics.

From rule engines to AI insights.

From dashboards to decision intelligence.

That clarity changed everything.

The Unexpected Reward

Today, people still ask questions.

Of course they do.

And I welcome them.

But the feeling is different now.

Instead of feeling drained, I feel grateful.

Because each question tells me that someone is curious.

Someone is exploring.

Someone wants to understand.

And now I have something meaningful to share.

Not just an answer.

A pathway.

When someone tells me,

“I read your Resource page, and now I understand what Favoriot is.”

That feels incredibly satisfying.

More satisfying than closing a sale.

Because understanding builds trust.

Trust builds relationships.

And relationships build ecosystems.

The Aha Moment

Looking back, I now see that the repeated questions were never the problem.

They were actually guiding me.

They were telling me exactly what needed to be documented.

Exactly what was needed was clarity.

Exactly what was needed was storytelling.

And once I finally organised all that knowledge into structured content, something powerful happened.

The pressure disappeared.

The message became scalable.

And the story of Favoriot could travel further than my own voice.

That was my real aha moment.

When people stop depending on your explanation and start learning from your ideas, you know something meaningful has been built.

Favoriot is not just about connecting devices.

It is about connecting understanding.

And that journey started with a simple realisation.

Sometimes, the most annoying repeated questions are actually the best teachers.

Now I am curious.

Have you ever experienced the same situation in your own journey?

People asking the same question again and again?

What did you do about it?

Did it frustrate you, or did it push you to build something better?

FAVORIOT Resources

From Classrooms to Critical Operations: The Truth About Favoriot’s Enterprise Role

They Thought Favoriot Was Just for Students.

I Let That Misunderstanding Linger for Too Long.

I need to admit something first.

This one is on me.

For years, people have come up to me and asked a question that always makes me pause.

“Dr Mazlan, is Favoriot only an education platform?”

Every time I hear that, I smile politely. I explain. I clarify. I move on.

But deep inside, I talk to myself.

How did we let this idea stick for so long?
Why didn’t we tell the story better?

Let me do this properly here. Slowly. Honestly. From the heart.

Because Favoriot was never born as an academic toy. It was never designed to live only inside labs, classrooms, or final-year projects. Favoriot was built as an enterprise IoT platform for real deployments, real operations, real risks, and real consequences.

Education came later. And it came for a reason.

Favoriot Was Built for the Real World First

When we started Favoriot, the vision was very clear.

Factories. Warehouses. Farms. Buildings. Cities.
Sensors are sending data every second.
Dashboards that people depend on, not admire.
Alerts that wake someone up at 3 a.m. because something is wrong.

That was the intention.

An enterprise IoT platform is not glamorous. It is not flashy. It does not impress with demos alone. It needs to survive power outages, unstable networks, noisy data, and human mistakes.

That is the world Favoriot was designed for.

Air quality monitoring, indoor and outdoor.
Gas detection in agriculture and manufacturing.
Cold chain and warehouse monitoring.
Energy usage. Environmental sensing. Operational visibility.

These are not student exercises. These are systems people rely on to protect assets, livelihoods, and, at times, lives.

And yes, many of these implementations cannot be publicly shared. Clients trust us with their data and their operations. Confidentiality is part of doing real work.

Ironically, that silence made people assume nothing was happening.

Maybe that’s where the misunderstanding started.

The Real Problem Was Never the Platform

Here is the uncomfortable truth.

The biggest challenge in IoT is not platforms.
It is not sensors.
It is not cloud infrastructure.

It is people.

Or more specifically, the lack of people who truly know how to build an IoT solution end-to-end.

Back in 2017, we offered a free plan. We thought adoption would be instant.

It wasn’t.

People signed up.
Then they stopped.
Nothing moved.

And I remember thinking, “Why is no one using it?“

The answer hurt a little.

They didn’t know how.

They knew dashboards from presentations.
They knew buzzwords from conferences.
They knew how to connect one sensor, sometimes.

But building a full solution?
Designing data flows?
Handling failures?
Understanding why data behaves badly in the real world?

That knowledge gap was huge.

From 2017 to 2022, I saw it everywhere. Universities. Startups. Even some companies. Everyone wanted IoT. Very few knew how to build it properly.

Why We Walked into Education

So we made a decision.

Not a pivot. Not a retreat. A foundation.

If people cannot build IoT solutions, no platform will ever matter.

I remember asking myself:
Do we complain about the talent gap, or do we help close it?

That is when we started working closely with educators. Training lecturers. Creating step-by-step tutorials. Supporting students not to pass subjects, but to understand systems.

That is why Favoriot content online often looks educational.

Not because we are an education-only platform.
But because education was the missing piece in the ecosystem.

We were not selling theory. We were teaching how to connect sensors, send data, manage devices, handle failures, and make sense of messy reality.

Education was not the destination. It was the on-ramp.

Two Worlds. One Platform.

Here is what many people missed.

While all this educational work was happening in public, Favoriot was quietly working with industry in parallel.

Two tracks. Same platform.

On one side, students and lecturers are learning how to build.
On the other, enterprises deploying systems that run daily operations.

The platform did not change.
The expectations did.

Students learn to make things work.
Enterprises demand that things not break.

That dual role was never a conflict. It was a strength.

Education feeds industry.
Industry validates education.

Yet we did not tell that story clearly enough. And for that, I take responsibility.

The Irony of Global Adoption

Here is another irony that few people realise.

Favoriot users come from all over the world. When someone subscribes, they build whatever they want.

We do not always know what devices they connect.
We do not always know what systems they deploy.
We only see data flowing.

Some of the most interesting use cases are completely invisible to us.

And that is exactly how a real platform works.

No hand-holding. No spotlight. Just infrastructure doing its job.

But again, silence creates assumptions.

If people don’t see it, they think it doesn’t exist.

This Is Not Just About Favoriot

This reflection is not only about correcting a misunderstanding.

It is about how we, as a country and as a community, think about capability.

We love importing solutions.
We love buying finished systems.
We rarely invest in learning how they are built.

Then we wonder why we depend on outsiders for everything.

IoT is not magic. It is engineering. It is discipline. It is patience. It is experience.

Platforms like Favoriot matter only when people know how to use them properly.

That is why education and enterprise must never be separated.

What I Wish People Would See

I wish people would stop asking whether Favoriot is for education or industry.

It has always been both.

Education builds builders.
Industry needs builders.

One without the other collapses.

Sometimes I ask myself:
If we had focused only on selling enterprise solutions, would the ecosystem be stronger today?

Honestly? No.

Without talent, platforms die quietly.

A Personal Reflection

I have spent my life in technology. Telecom. IoT. Smart systems. Startups.

The pattern is always the same.

People rush to buy tools.
Very few invest in learning how to use them well.

Favoriot’s story is a reminder to me, too.

Technology without understanding is decoration.
Understanding without real deployment is a fantasy.

We need both.

My Message to Educators

Do not treat IoT platforms as demo tools.

Treat them as environments where students learn responsibility.

Teach failure.
Teach troubleshooting.
Teach why things break.

That is how builders are formed.

My Message to Industry

Do not dismiss platforms you see in universities.

Those environments are where your future engineers are learning.

Support them. Challenge them. Hire them.

You will thank yourself later.

My Message to Policymakers and Leaders

If you want digital capability, stop funding only deployments.

Fund learning.
Fund training.
Fund local platforms and ecosystems.

Ownership starts with understanding.

And Finally, My Message to You

If you are reading this and you once thought Favoriot was “just for education”, I hope this piece helped.

If you already knew the bigger picture, help me tell the story better.

Because platforms do not build ecosystems.
People do.

And ecosystems take time, patience, and honesty.

I’m still learning that myself.

What about you?

Have you seen similar misunderstandings in your work or industry?
Drop your thoughts in the comments. I read them all.

Why Becoming a Producer Nation Still Keeps Me Awake at Night

There was a moment some time ago when I paused in the middle of a talk and looked around the room. Not because I forgot my slides. Not because I lost my train of thought.

But because something heavier crossed my mind.

I was surrounded by capable people. Young engineers. Curious technologists. Lecturers who cared. Students who wanted to build something meaningful.

And a question whispered quietly in my head.

What kind of future are we actually preparing them for?

That question refuses to leave me. It follows me into meetings, classrooms, and late-night reflections. It comes back whenever I see another imported system being installed, another local prototype ignored, another talented graduate settling for work that barely scratches their potential.

This is not about blaming anyone.
This is about being honest with ourselves.

The comfort trap we rarely talk about

Let me say this plainly.

Being a consumer nation feels safe.

You buy what already works.
You rely on someone else’s research.
You avoid the pain of early failure.

There is no embarrassment in using technology built elsewhere. We all do it. I do it too. The problem begins when using becomes the end of the story.

When a country only consumes, it slowly forgets how to create.

Companies no longer need deep technical teams.
Jobs no longer demand strong problem solvers.
Graduates are hired, but not challenged.

And when skills are not demanded, they are not rewarded.

I have watched this cycle quietly repeat itself.

Low demand for advanced skills leads to low salaries.
Low salaries keep household income stuck.
And national ambition stays trapped in speeches instead of results.

I often ask myself, what is the point of producing bright graduates if the economy only needs users?

What changes when a nation chooses to build

A producer nation changes the conversation entirely.

Instead of asking, “What can we buy faster?”
It asks, “What can we build better?”

The moment local companies start developing their own products, something shifts inside the system.

Skills suddenly matter.
Experience becomes valuable.
Talent is no longer replaceable overnight.

Companies compete for people who can design, test, deploy, and maintain real systems. Salaries rise not because someone demands it, but because value is being created on the ground.

This is how strong economies grow. Quietly. Patiently. Through capability, not dependency.

I remind myself often that a producer nation is built by people who are willing to be uncomfortable first.

The painful truth about local innovation

Here is where the story becomes uncomfortable.

Most local startups do not fail because their ideas are bad.
They fail because nobody buys from them early enough.

There is a fragile phase every builder faces.
The search for the first ten customers.

Without those early believers, there is no runway. No learning loop. No chance to improve.

And this is where I sometimes feel uneasy.

We encourage innovation.
We fund research.
We celebrate prototypes.

Yet when it is time to adopt, trust disappears.

I catch myself thinking: why do we support people in building, but hesitate to stand beside them when they are ready?

Without local adoption, many promising efforts fade away. Not loudly. Quietly. One by one.

Universities are not broken. Expectations are.

For years, I have heard the same complaint repeated.

“Universities are not producing commercial products.”

That statement misses the point.

Universities were never meant to be factories.
They are meant to be places where thinking goes deep.

They excel at long-term exploration.
They are strong at building early prototypes.
They train minds, not sales pipelines.

The problem starts when we expect universities to sprint like startups.

I often tell myself, you do not ask a marathon runner to win a 100-meter dash.

When companies bring real, long-term problems to universities, something powerful happens. Research becomes grounded. Students work on issues that matter. And ideas mature with purpose.

The missing bridge between lab and market

There is a wide gap between a working prototype and a product that survives in the field.

Many people underestimate this gap.

A system that works in a lab has not yet faced real users, harsh environments, unreliable networks, or unexpected behaviour. This is where companies must step in.

Universities build understanding.
Companies build resilience.

When they work separately, both struggle.
When they move together, progress accelerates.

This bridge was not built overnight. It takes patience, shared goals, and trust.

Why the first believer matters most

Every global success begins at home.

Before the world trusts you, someone local must.

That is why early adopters matter so much. Especially large organisations and government bodies.

Being the first customer is not charity.
It is leadership.

It gives builders confidence.
It creates reference stories.
It signals belief.

Belief, more than marketing, opens doors beyond borders.

Why I chose to build instead of complain

At some point, reflection was not enough.

I asked myself a harder question.

If I believe in building local capability, what am I personally doing to make it happen?

That question led me to Favoriot.

Favoriot was never about flashy dashboards.
It was about enabling builders.

A place where students move beyond demos.
Where startups test ideas without fear.
Where organisations grow solutions they understand and own.

I wanted a platform that supports responsibility, not just visibility.

A quiet piece of advice I return to often

Do not wait for perfect systems.
Do not wait for perfect policies.
Build anyway.

To students
Choose projects that solve real problems.

To universities
Work with companies that think beyond short grants.

To companies
Invest in local capability, even when it feels slower.

To decision-makers
Adopt local solutions early, not after they succeed elsewhere.

My invitation to you

If you believe our future depends on building, not just buying.
If you believe talent deserves meaningful challenges.
If you believe local solutions deserve real trust.

Then take one step.

Support a local product.
Adopt a local system.
Encourage someone who is trying.

And if you are looking for a place to start building, experimenting, and growing with confidence, explore Favoriot.

Not as software.
But as a choice.

I would love to hear your thoughts.
Are we ready to move from comfort to courage?

Crafting Impactful Final Year Projects: A Guide

I’ve sat on many evaluation panels over the years.

Different universities. Different rooms. Different faces.

But strangely, the pattern is always familiar.

Students walk in carrying posters, prototypes, sometimes with wires still exposed, sometimes with boxes made from recycled lab scraps. They look nervous. Excited. Hopeful. Tired.

And almost every presentation begins the same way.

“This project is about…”
“The objective of this project is…”

I sit back in my chair and quietly think to myself, Ah… here we go again.

Because at that moment, something important is missing.

The Moment Evaluators Lean In or Tune Out

When I evaluate a Final Year Project, I’m not hunting for perfection. I’m not expecting commercial-grade products. I’m not counting how polished the slides are.

I’m listening for one thing.

Do you understand why you built this?

Many students rush straight into objectives, features, and functions. But they forget to set the stage. They forget to frame my mind.

Without a background.
Without a problem that feels real.
Without a pain point that matters.

And when that happens, evaluators start asking questions not because the project is weak, but because the story is unclear.

Help me care first, I always think. Then help me understand.

Start With Pain, Not Purpose

The strongest projects I’ve seen don’t start with what was built.

They start with what hurts.

A system that fails silently.
A manual process that wastes hours.
A safety issue nobody notices until it’s too late.
A data gap nobody talks about.

When students explain the background clearly, something shifts. The room wakes up. The evaluator’s brain starts connecting dots.

Only after that does the objective make sense.

Because now, the solution has a reason to exist.

Scope Is Not a Weakness

Another thing I notice again and again.

Projects that look “complete,” but aren’t honest about their limits.

Students are afraid to admit constraints. Limited time. Limited budget. Limited access to hardware. Limited skills.

But here’s the truth.

A clear scope shows maturity.

When you explain what you chose not to build and why, you’re telling me you understand trade-offs. You understand reality. You’re not pretending.

That impresses evaluators more than pretending everything is done.

The Story of Struggle Matters More Than the Result

Some of the most memorable presentations weren’t the ones that worked perfectly.

They were the ones where students said:

“We tried this. It failed.”
“So we changed this.”
“It broke again.”
“Here’s why we finally chose this approach.”

That tells me you didn’t just follow a tutorial. You wrestled with the problem. You learned where things break.

And that’s exactly what real engineers, builders, and problem solvers do.

Architecture Is Not Just a Diagram

I’ve lost count of how many times I’ve seen architecture diagrams that don’t reflect reality.

Devices sending data to nowhere.
Networks are magically working.
Platforms floating without context.

When I ask, “Where does the data go next?”
Silence.

Architecture is not an artwork. It’s a thinking tool.

If you can’t explain how data moves from device to network, from network to platform, from platform to application, then you don’t fully own your system yet.

This is where supervisors play a big role. And this is where students must slow down and really understand what they are drawing.

Prototypes Don’t Need to Look Pretty

Some students apologise for their mock-ups.

“Sorry, sir, this is just a box.”
“Sorry, sir, we used old parts.”

I always smile.

Because that’s not what I’m judging.

What excites me is when students act out real scenarios. When they simulate how users interact. When they demonstrate behaviour, not just hardware.

I still remember sitting inside a car to experience a student-built parking system. That wasn’t about polish. That was about empathy.

The Question That Makes Everyone Nervous

Then comes the part that always makes students laugh nervously.

“So… who would buy this?”

Suddenly, the room gets quiet.

Many students talk about the cost of components. Few talk about customers. Fewer talk about value.

I’m not expecting a full business plan. I’m testing awareness.

Do you understand that solutions exist to be used?
Do you know who benefits from what you built?

Because a project that solves a real problem for a real group of people already has more value than one that only looks good on demo day.

When Systems Break, Thinking Is Revealed

The most important questions often come at the end.

“What happens if the system fails?”
“How do you troubleshoot this?”
“What would you check first?”

These answers reveal everything.

They show whether learning happened.
They show whether the student truly built the system or just assembled it.

In team projects, I watch carefully. Everyone should understand their role. Everyone should be able to support each other. Silence from team members tells its own story.

Forty Years of Change, One Pattern That Remains

I’ve watched student projects evolve from the 1980s until today.

Better tools. Better access. Better exposure.

Yet one problem remains.

Projects restart from zero every year.

Limited budgets force repetition. The same sensors. The same ideas. The same level of impact.

Imagine if universities treated projects as living systems.

One cohort builds the base.
The next improves it.
Another adds data analysis.
Another adds intelligence.

That’s how meaningful systems grow.

Especially in IoT, where data collected over time becomes more valuable than the device itself.

My Advice to Students and Educators

If you’re a student, remember this.

Your project is not judged by perfection.
It’s judged by understanding.
Clarity.
Honesty.
Growth.

Tell the story of your problem.
Explain your decisions.
Show your struggles.
Own your limits.

If you’re an educator or supervisor, help students see beyond grades.

Teach continuity.
Teach systems thinking.
Teach them to build on each other’s work.

Because the real world doesn’t reset every semester.

And the most important lesson a Final Year Project can teach is not how to build something that works.

It’s how to think when things don’t.

The Moment the Smart City Dashboards Stopped Impressing Me

There was a time when I was impressed by command centres.

Rows of screens.
Maps glowing in neon colours.
Charts are moving in real time.
Operators are pointing at dashboards like air traffic controllers.

It looked powerful.
It looked serious.
It looked… convincing.

But one day, standing quietly at the back of the room, I caught myself thinking something uncomfortable.

If one screen goes dark, who notices?
If the data contradicts another system, who decides?
If something breaks at 2 a.m., who actually understands what is happening?

That was the moment the screens stopped impressing me.

Because cities are not run by visuals.
Cities are run by clarity.

And clarity does not come from dashboards alone.

How Cities Slowly Accumulate Silos Without Realising It

Most local councils chose not to fragment.

Fragmentation happened to them.

Projects arrived one by one.
Budgets were approved year by year.
Each initiative solved a real problem at the time.

Flood monitoring came first.
Then air quality.
Then lakes.
Then traffic.
Then parking.

Each project was justified.
Each vendor delivered.
Each system worked.

Individually.

What nobody planned for was the moment when all these systems would need to speak to each other.

So the command centre slowly became a collection of disconnected truths.

Each dashboard told its own story.
None of them told the whole truth.

When a Dashboard Is Mistaken for a Platform

I often hear this sentence.

“Yes, we already have a smart city platform.”

Then I look closer.

What I see is usually a visual layer.
A presentation surface.
A beautifully designed window.

But behind it, there is no device management.
No rule engine.
No action triggers.
No real-time orchestration.

Just data being shown.

And showing data is not the same as running a city.

A true platform does not just display.
It listens.
It reacts.
It remembers.
It connects.

Two Types of Data That Rarely Shake Hands

Cities live in two data worlds.

The first world is structured, administrative, and familiar.

Assets.
Licences.
Collections.
Population data.
Facilities.

This data is critical. It reveals the city’s shape. It is refreshed periodically and often lives inside systems branded as urban observatories.

The second world is restless.

Sensor data.
Live streams.
Alarms.
Failures.
Spikes.
Drops.

This is IoT data.
It does not wait politely.
It arrives when it wants.
It demands attention.

The mistake happens when we treat both worlds as if they behave the same way.

They do not.

GIS and Digital Twins Without Real-Time Truth

Many councils have strong GIS platforms.

Layers upon layers of insight.
Maps that tell stories about people, land, and risk.

Some go even further with digital twins.
Virtual representations of buildings, roads, and infrastructure.

I admire these efforts.

But without live sensor input, these systems are frozen in time.

They show structure.
Not behaviour.

A city is not just where things are.
It is how things change.

Without IoT data, even the most beautiful digital twin is only a photograph, not a mirror.

Why an Integrated IoT Platform Is Not Optional Anymore

At some point, cities reach a tipping point.

They stop asking for new dashboards.
They start asking better questions.

Why did flooding worsen after that traffic upgrade?
Why does air quality dip only in specific zones?
Why do alarms trigger too late?

These questions cannot be answered inside silos.

They require correlation.

This is where an integrated IoT platform matters.

Not to replace everything.
But to connect everything.

A layer where data from rivers, rain, air, traffic, parking, and buildings can coexist.
A place where patterns emerge.
A place where decisions are supported, not guessed.

This is the role of IoT middleware.
This is where platforms like FAVORIOT were designed to sit.

The Fantasy of One Platform to Rule Them All

Every city dreams of simplicity.
Every vendor dreams of being central.

The idea of one master platform controlling everything is seductive.

But reality is less romantic.

Platforms are built with different goals.
Vendors protect their niches.
Legacy systems do not disappear quietly.

Trying to force everything into one system usually creates resistance, delays, and disappointment.

Cities do not need domination.
They need coordination.

The Quiet Risk Nobody Likes to Talk About

There is a dangerous sentence I hear too often.

“We don’t mind. Let the vendor manage everything.”

It sounds efficient.
It sounds hands-off.

Until the day the council asks for raw data.
Or integration rights.
Or historical access.

And discovers they cannot.

No API.
No export.
No control.

That is vendor lock-in.
And by then, it is too late to complain.

A smart city without data ownership is not smart.
It is dependent.

Procurement Is the Real Smart City Strategy

Smart cities are not won in control rooms.

They are won in procurement documents.

When councils specify openness.
When they demand interoperability.
When they insist on owning their data.

That is when cities protect their future.

Technology can always be upgraded.
Contracts are harder to undo.

Integration Is an Act of Maturity

I no longer believe in replacing everything.

I believe in respecting what already works.
Connecting what matters.
Opening what was once closed.

Legacy platforms should remain.
Specialised systems should continue.
But data must flow.

Sometimes that means managing two or three core platforms instead of one.

That is not failure.
That is realism.

Why I Keep Writing About This

I am not chasing trends.
I am chasing calm.

Calm operators.
Calm decision-makers.
Calm cities that respond instead of react.

When systems are integrated, nights are quieter.
When data is shared, trust grows.
When platforms cooperate, leaders sleep better.

If you are building a smart city, pause before asking for another screen.

Ask instead:
Can this system talk?
Can it share?
Can it last?

If this reflection sounds familiar, I would love to hear from you.

What have you seen in your city?
Where did silos slow you down?
What worked when integration finally happened?

Drop your thoughts in the comments.
Let us learn from each other and build cities that truly understand themselves.

Smart Cities in Malaysia – Between Beautiful Documents and Real Implementation

There is a kind of silence I remember very clearly.

Not the silence of an empty room.
But the silence appears when too many slides are shown, too many big words are used, and too few honest questions are asked.

I was sitting in yet another Smart City presentation. Everyone was talking about master plans, KPIs, ISO standards, indicators, and rankings. The slides looked polished. The diagrams were neat. The language sounded confident.

Yet inside, a quiet question kept repeating.

Who will take care of this after the launch?
Who will wake up when the system fails?
Who will face the public when citizens are angry?

Those questions rarely appear on slides.

And that, for me, is where the real Smart City problem in Malaysia begins.

Why We Talk About Smart Cities at All

Smart Cities are not about technology.

They are about people.

They are about parents stuck in traffic every morning.
Children breathe unhealthy air.
Small business owners suffer when flash floods arrive without warning.

I often say this, and I truly believe it.

The final goal of a Smart City is very simple.

People can live healthier lives.
People can live happier lives.
Cities can run without constant chaos.

That’s it.

Not rankings.
Not awards.
Not plaques on office walls.

Yet somewhere along the way, we lost that simplicity.

When Everyone Wants to Be “Smart”

Today, almost everyone wants the Smart City label. Some go further and call themselves “AI Cities”.

I usually smile when I hear that.

Which AI?
Where is the intelligence?
Or is it just a new signboard?

Many systems branded as AI are simply basic automation. This is not a technology problem. It is a misunderstanding.

What troubles me more is this.

Some cities work quietly, building systems that actually function, yet receive no recognition because they never submitted an application. Others receive recognition early simply because they know how to fill out forms.

That’s when we learn a hard truth.

Recognition does not always reflect maturity.

From 30,000 Feet to 3 Feet

To be fair, Malaysia does have a solid Smart City framework.

On paper, it makes sense.

At 30,000 feet, there is the national master plan.
At 3,000 feet, there are state-level blueprints.
At ground level, around 3 feet, there should be detailed action plans for local councils.

Everything looks structured.

But in reality, many councils are stuck somewhere in between.

Some are still writing plans.
Some are experimenting with pilot projects.
Very few are running systems consistently, day after day.

Not because they don’t care.
Not because they are lazy.

But because something fundamental is missing.

Delivery structure.

Command Centres That Feel Empty

I have visited many command centres.

The name sounds powerful. Command centre. It feels important.

But once inside, the scene is often the same.

CCTV screens.
Live video feeds.
A few officers are watching.

That’s all.

I quietly ask myself.

Where is the data integration?
Where is the analysis?
Where are the decisions driven by this data?

A command centre should be the brain of the city.

Not just its eyes.

Imagine traffic data, air quality, noise levels, parking systems, citizen complaints, legacy databases, all connected and analysed together.

First, we know what has happened.
Then, we understand why it happened.
Next, we anticipate what might happen.
Finally, we know what action to take.

This is where technology truly matters. Not to impress, but to guide decisions.

The Challenges We Rarely Admit

Since around 2015, I have seen the same issues repeat.

Budget That Is Never Enough

Local councils are not money-making machines.

They rely on limited revenue sources. Assessment taxes. Parking fees. Licenses.

With limited funds, choices become limited too.

Projects that generate revenue or reduce costs often get priority. Long-term social impact projects struggle to survive.

Risk-heavy concession models usually favour large companies with deep pockets. Smaller local players, often full of ideas and energy, get pushed aside.

Sometimes I ask myself quietly.

Do we really want local ecosystems to grow?
Or are we just choosing the easiest path?

Projects Without Guardians

This one hurts the most.

Many Smart City projects are launched with excitement. Press conferences. Posters. Promotional videos.

A year later, the system is silent.

No maintenance.
No monitoring.
No clear ownership.

The project becomes a white elephant.

Not because the technology failed.
But because no one was assigned to take care of it.

Skills Gap Is Real

Smart Cities demand new skills.

Data management.
IT infrastructure.
Commercial thinking.
Long-term contract handling.

Many council officers come from strong urban planning backgrounds. They are good at what they do.

But we cannot expect them to suddenly manage complex digital systems without proper support.

This is not an individual failure. It is a structural one.

Fragmented Governance

For solution providers, one simple question often becomes complicated.

Who should we speak to?

Without a clear focal point, discussions lose direction. Time is wasted. Trust slowly fades.

One Answer I Strongly Believe In

If there is one thing that matters most, it is not technology.

It is a Delivery Unit.

A dedicated team.
Given authority.
Given responsibility.
Given continuity.

This unit becomes the caretaker of the entire Smart City lifecycle.

From strategy.
To execution.
To daily operations.
For long-term maintenance.

When this unit exists, everything changes.

Communication becomes clear.
Ownership becomes visible.
Projects do not get abandoned.
Citizens start feeling real benefits.

Smart City stops being a document.
It becomes a service.

Why I Still Have Hope

I am not writing this out of frustration.

I am writing because I still believe.

I believe our local councils are capable.
I believe our local talent is strong.
I believe technology is just a tool, not the answer.

What we need is the courage to admit weaknesses and the wisdom to build the right structure.

Smart City is not a race.
It is a responsibility.

If we want public trust, we must start taking care of what we build.

And it begins with one honest question.

Who will make sure this city still works tomorrow morning?

If this piece made you pause and think, I would love to hear your thoughts.
Leave a comment. Let’s talk.

Building IoT Alone vs Building Together: Why Local Platforms Change Everything

I want to share something that has been sitting heavily in my heart for a while.

Every time I speak to engineers, lecturers, startups, or research teams, I ask a simple question.

“What IoT platform are you using?”

The answers came quickly.

From abroad.
From overseas.
From a big global brand.
Or… “We built our own server.”

I nodded. I smiled. But inside, something felt heavy.

Why are we still doing this to ourselves?
Why do we keep believing the best tools must come from somewhere else?

That moment stayed with me long after the talk ended

We Are Obsessed With Dashboards, But Forget the Foundation

Let me be honest.

Many IoT teams I meet are not obsessed with devices. They are obsessed with dashboards.

Big screens.
Live charts.
Green indicators that say “OK”.

Nothing wrong with that. Dashboards matter. Visibility matters.

But when I dig deeper and ask, “Who do you actually work with behind that platform?”
Silence.

They have never met the platform provider.
Never spoken to an engineer there.
Never sat down to plan a market together.

How do you build something meaningful when you do not even know who is behind the engine?

That is the first quiet weakness nobody talks about.

Depending on a Distant Platform Feels Safe. Until It Isn’t.

Using a foreign platform feels comfortable.

It feels established.
It feels global.
It feels like you are standing on something big.

But distance has a price.

No close collaboration.
No shared story.
No joint effort to help your product grow beyond a pilot.

When something breaks, you open a ticket.
When something stalls, you wait.
When you want to commercialise, you are on your own.

I thought to myself, is this really what building an ecosystem looks like?

Local Platforms Are Not “Second Choice”. They Are Strategic Choices.

This is where my heart always leans forward.

When a university, a startup, or a solution provider works with a local IoT platform like Favoriot, something changes.

You do not just get software.

You get people.
You get conversations.
You get arguments on whiteboards.
You get someone who cares because your success is their success, too.

We can sit together.
We can shape the solution together.
We can plan how it reaches the market together.

That closeness is not a luxury. It is a multiplier.

Cross-Marketing Is Not a Buzzword. It Is Survival.

Let me put this simply.

Your market is never big enough on its own.
Neither is mine.

But when we walk into each other’s markets together, something opens up.

Your customers see us.
Our users see you.
Stories start travelling.

If a project uses our platform, we talk about it.
We highlight it.
We share it across our channels.

And no, this is not charity.

It is shared growth.

I remember thinking, why should every company shout alone when we can amplify each other’s voices?

Bundling Is About Completing the Story, Not Selling More Stuff

Here is another truth most people avoid.

Almost nobody builds everything themselves.

You may focus on air quality.
But your hardware comes from overseas.
Your connectivity comes from someone else.
Your cloud might sit on Azure or AWS.

That is normal.

What matters is how these pieces come together for the customer.

A single product often feels incomplete.
A bundled solution feels finished.

Your sensor plus our platform.
Your analytics plus our alerts.
Your service plus our visibility.

The customer does not want components.
They want relief.
They want clarity.
They want answers.

Bundling is not about pushing more.
It is about removing friction.

Ego Is the Silent Killer of IoT Ecosystems

This is the part that makes people uncomfortable.

Ego.

The belief that “we can do everything ourselves.”
The fear that collaboration means losing control.
The worry that sharing space means shrinking your brand.

I have seen this mindset slow down brilliant teams.

I told myself, collaboration is not surrender.

Working with partners does not make you smaller.
It makes you reachable.

It gives you angles you cannot create on your own.

Universities, Startups, Platforms. We Need Each Other.

Universities have ideas.
Startups have hunger.
Platforms have structure.

Separately, we struggle.
Together, we move.

When a university builds a project on a local platform, that project does not end as a report.
It becomes a case study.
A reference.
A stepping stone to something real.

When a startup launches on a local platform, it does not just deploy.
They learn how to sell.
How to explain value.
How to survive their first customers.

I often whisper to myself, this is how ecosystems are supposed to feel.

Why This Matters More Than Ever

We talk about national capability.
We talk about digital sovereignty.
We talk about nurturing local champions.

But these words mean nothing if we keep outsourcing belief.

Supporting local platforms is not about patriotism.
It is about practicality.

Local platforms understand local constraints.
Local regulations.
Local customers who call you at 2 a.m.

And when you grow, they grow with you.

A Quiet Invitation

If you are building IoT solutions today, pause for a moment.

Ask yourself:

Who do I actually collaborate with?
Who knows my product beyond a ticket number?
Who will walk with me to the market?

If the answer feels distant, maybe it is time to rethink.

Not to abandon global tools.
But to anchor your growth closer to home.

I believe ecosystems are built by hands that reach out, not by fingers that point outward.

Let us talk.
Let us partner.
Let us bundle, cross-promote, and craft stories that travel beyond dashboards.

Contact Favoriot and let’s build IoT solutions together.

I would love to hear your thoughts.
Share your experience in the comments.

When Data Leaves the Country, Control Leaves With It

A personal reflection on why I insisted on an Enterprise IoT Platform with on-premise deployment

There are moments in a founder’s life when you stop talking about features.

You stop talking about dashboards.
You stop talking about protocols.
You even stop talking about scale.

And you start talking about control.

This was one of those moments.

I remember sitting quietly after one of our internal briefings, staring at the whiteboard filled with arrows, boxes, and deployment diagrams. Everyone had left the room. The air was still.

Why am I pushing so hard for this Enterprise Plan?
Why does this feel heavier than just another pricing tier or feature release?

Then it hit me.

This was not about software.
This was about sovereignty.

And once you see it that way, you can never unsee it.

From owning a kitchen to owning the whole restaurant

For years, I used a simple analogy when explaining IoT platforms.

If you are on a shared cloud platform, you are like a chef renting a kitchen. You can cook. You can serve. But you do not own the space. You follow house rules. You live with limits.

The Enterprise Plan is different.

It is not about owning the kitchen anymore.
It is about owning the whole restaurant.

The building.
The keys.
The doors.
The data flows.
The servers are sitting quietly in your own premises.

When you own the restaurant, no one tells you when to close. No one caps how many customers you can serve. No one decides where your ingredients come from.

That is the mindset behind the Enterprise IoT Platform.

The moment I realised cloud is not always the answer

For a long time, cloud felt like the default answer to everything.

Fast.
Flexible.
Convenient.

I believed in it. I still do, for the right use cases.

But over the years, as I spoke to large organisations, city operators, government agencies, and critical infrastructure owners, a pattern kept repeating itself.

“We don’t want our data outside the country.”
“We need to know exactly where the servers are.”
“We cannot afford external dependencies for this system.”
“This data is too sensitive.”

At first, some people dismissed these concerns as paranoia.

I did not.

Because when you are dealing with traffic lights, water systems, energy grids, and public safety sensors, paranoia is just another word for responsibility.

What happens if the platform is outside the country and something goes wrong?
Who takes control when connectivity is lost?
Who answers when an entire city goes dark?

These are not theoretical questions. These are operational nightmares waiting to happen.

Data sovereignty is not a buzzword when infrastructure is involved

Data sovereignty sounds abstract until you put real consequences next to it.

Imagine a critical infrastructure monitoring system managed by a platform hosted overseas. One day, there is a major failure.

Power outage.
Network disruption.
Access blocked.

The local operators are standing there, staring at blank screens, unable to take control because the system that runs their infrastructure is not physically within reach.

That is unacceptable.

This is why on-premise deployment matters.

Not because it sounds serious.
Not because it looks impressive in a proposal.

But because control must stay with those who are accountable.

This thinking shaped every part of the Enterprise IoT Platform plan.

AI made the stakes even higher

If IoT data is sensitive, AI makes it explosive.

AI models learn from data.
Patterns.
Behaviours.
Weak points.

When AI touches critical infrastructure data, the question is no longer just “where is my data?”

It becomes “who understands my system better than I do?”

That was the turning point for me.

If AI is going to sit on top of IoT data, then the data must never leave the country.

This is not about fear.
This is about governance.

Every country I speak to says the same thing, whether it is Malaysia, Indonesia, the Middle East, or Europe.

“We want AI. But we want our data at home.”

The Enterprise Plan was designed to respect that reality.

Unlimited API is not a luxury; it is a survival

One detail that often gets overlooked is API limits.

People ask me, “Why unlimited API? Isn’t that excessive?”

Let me paint you a picture.

A manufacturing line monitors machines every second.
One sensor. One data point per second.
Multiply that by hundreds of machines.
Multiply again by shifts, days, months.

Suddenly, 500,000 API calls per day is not generous. It is restrictive.

The Developer Plan has limits because it should. It is built for builders, experimentation, and controlled scaling.

But enterprise environments do not experiment. They operate.

If you throttle data in an industrial environment, you are not saving costs. You are introducing blind spots.

Unlimited API is not about indulgence.
It is about continuous visibility.

Two very different enterprise realities

As I refined this plan, two clear deployment models kept emerging.

1. The white-label service provider model

Some organisations do not want to sell hardware.
They want to sell managed IoT services.

They do not want to build a platform from scratch. That path is expensive, slow, and painful.

So they white-label the Enterprise IoT Platform.

Their brand.
Their customers.
Their business logic.

They plug in their agricultural sensors, industrial devices, and vertical solutions, and run everything on their own enterprise platform.

Thousands of customers.
One controlled system.

I have seen how powerful this model can be when done right.

2. The smart city and government deployment model

Then there are cities.

Cities are different.

They already have many solutions. Parking. Flood sensors. Air quality. Lighting. Waste.

The problem is not a lack of data.
The problem is fragmentation.

Every system has its own dashboard. Its own vendor. Its own silo.

Local councils want a single platform, deployed on-premises, where everything comes together.

In some cases, councils cannot do this alone.

That is where state-level deployment makes sense.

One enterprise platform owned by the state.
Local councils connect their data.
Data stays within the country.
Visibility scales across regions.

It is pragmatic. It is cost-aware. It respects sovereignty.

This is bigger than one platform

As I reflect on this journey, I realise something.

The Enterprise IoT Platform is not just a product decision.
It is a philosophical stance.

It says:

You should own your data.
You should control your infrastructure.
You should not outsource accountability.

In a world rushing towards convenience, this is a reminder that responsibility still matters.

A quiet call to builders, cities, and leaders

If you are building systems that people depend on, ask yourself one simple question.

When things go wrong, who truly has control?

If the answer is unclear, it might be time to rethink how your platform is deployed.

I did.
And that rethink led us here.

I would love to hear your thoughts.
Where do you draw the line between convenience and control?
Share your reflections in the comments.

Why We Believe Universities Need a Favoriot Platform Ecosystem, Not Just IoT Accounts

I shared this idea in a recent product presentation, but the more I reflect on it, the more I feel this deserves to be written down properly. Slowly. Honestly. With feeling.

Because this is not just about plans and pricing.
This is about how we teach, how we learn, and how knowledge grows over time.

I remember pausing for a moment before the session began.
“Do people really see this problem yet?” I asked myself.

Most do not. And that is exactly why I want to tell this story.

The quiet problem nobody talks about

For years, I have watched how IoT is taught in universities.

Students are told, “Go subscribe.”
Lecturers say, “Use whatever tools you can find.”
Labs run on goodwill, workarounds, and personal accounts.

On the surface, it looks fine.

Free plans here.
A few paid plans there.
Some students pay out of pocket.
Some lecturers try to stretch limited lab budgets.

But beneath that surface, something feels broken.

I thought to myself, this is not how serious engineering should feel.

IoT is not a hobby once it enters a lab.
It is not a toy when it becomes a Final Year Project.
It is not casual when research data needs months, sometimes years, to mature.

Yet we treat the tooling like disposable apps.

Individual accounts versus institutional thinking

Most users experience Favoriot through individual plans. Free. Lite. Beginner. Developer.

That makes sense at the start.

You are curious.
You want to test.
You want to learn.

But universities are not individuals.

They are systems.

And systems need structure.

What usually happens today is this:

A student creates an account.
They collect data for a semester.
They graduate.
The account disappears.
The data disappears.
The knowledge disappears.

And every time this happens, I feel a quiet sense of loss.

Because data is not just numbers.
Data is effort.
Data is learning.
Data is time that never comes back.

The moment the question became clear

During the session, I asked a simple question.

What if universities could manage IoT accounts the way they manage labs?

What if, instead of hundreds of disconnected student subscriptions, there was one administrator, one place of control, one long-term memory?

That question changed everything.

I remember thinking, this is the missing layer.

What an IoT Ecosystem Plan really means

The Favoriot IoT Ecosystem Plan is not a fancy label.

It is a mindset shift.

Instead of students owning accounts, the institution owns the ecosystem.

One administrator manages a pool of plans.
Beginner. Lite. Developer.
Whatever fits the teaching or research need.

Accounts can be allocated.
Accounts can be rotated.
Accounts can be reused.

No chaos.
No loss.
No, starting from zero every semester.

A lab that finally makes sense

Imagine a lab with thirty Beginner plans.

The admin assigns ten accounts for this semester’s lab class.
Students log in.
They build.
They experiment.
They learn.

Next semester, the same accounts are reused by a new cohort.

I smiled when I explained this part.
Because this is how labs should work.

Not emotional budgeting.
Not last-minute subscriptions.
Not students asking, “Sir, do I really need to pay for this?”

Final Year Projects without financial anxiety

Final Year Projects are intense.

Students are already under pressure.
Deadlines.
Expectations.
Demonstrations.

Now add one more burden: the cost of tools.

I paused again when I talked about this.
“Why are we doing this to them?” I wondered.

Under the ecosystem plan, the department allocates accounts to FYP students.

No personal subscriptions.
No awkward reimbursements.
No half-built systems because the plan expired.

Just focus.
Just building.
Just learning.

Research data that does not vanish

This part matters deeply to me.

Research does not run on semesters.

Some datasets need months.
Some need a full year.
Some become valuable only after long observation.

In individual accounts, when a researcher leaves, the data often goes with them.

With an ecosystem plan, the data stays.

The account belongs to the institution.
The history remains intact.
The next researcher continues the story.

I remember thinking, this is how real research continuity should feel.

One dashboard. One view. One sense of control

Administrators often feel blind.

Who is using what?
Who is stuck?
Which lab is active?
Which accounts are idle?

An integrated dashboard changes that.

You can see progress.
You can spot gaps.
You can improve training.

This is not about surveillance.
This is about care.

Care for students.
Care for lecturers.
Care for outcomes.

Not one-size-fits-all, and that is the point

Some universities need thirty Beginner plans.
Some need seventy.
Some mix Beginner with Developer plans.

That is why ecosystem plans are quoted, not clicked.

Because education does not fit into neat boxes.

I told myself, flexibility is respect.

Respect for different teaching styles.
Respect for different research scales.
Respect for different budgets.

Why I feel strongly about this

I have spent decades in education, industry, and startups.

I have seen what happens when systems are built for convenience instead of continuity.

And I have also seen what happens when institutions think long-term.

This ecosystem idea is not about selling more plans.
It is about lifting the quality of learning.

It is about treating IoT education as a serious craft.

A quiet invitation

If you are a lecturer, ask yourself this:

Are your students building knowledge, or just finishing assignments?

If you are a researcher, ask this:

Will your data still matter when you move on?

If you are an administrator, ask this:

Is your IoT lab a collection of accounts, or a living system?

I know my answer.

I believe universities deserve an IoT ecosystem that grows with them, remembers with them, and supports the next generation better than we were supported.

If this idea resonates with you, I would love to hear your thoughts.

Drop a comment.
Challenge it.
Improve it.

That is how ecosystems begin.

Why We Want Students to Struggle a Little When Learning IoT

I want to be honest with you.

Every time I walk into a university or polytechnic to talk about IoT, I already know the answer before I ask the question.

“What platform are you using for your final year project?”

The answers come fast. Almost automatic.

One particular platform. That has …
A mobile app.
Lots of YouTube tutorials.
GitHub samples.
Forums everywhere.

I nod. I smile.

I’ve heard this story many times.

And then comes the follow-up question.

“Why that platform?”

The answer is almost always the same.

“Because it’s easy.”
“Because there’s a mobile app.”
“Because seniors used it.”
“Because everything is already there.”

At that moment, a quiet thought always crosses my mind.

Easy today, but are you ready for tomorrow?

This blog is not about criticising students. Far from it.

It is about explaining why I believe students need to struggle a little when learning IoT. And why Favoriot was built the way it is.

The Comfort Trap Students Fall Into

I understand why students choose platforms that feel comfortable.

You connect a sensor.
Data appears on your phone.
You show it to your supervisor.
Demo done.

No need to build dashboards.
No need to understand protocols.
No need to worry about servers or data pipelines.

It feels good.

But comfort can be deceptive.

I asked myself, are we training students to build IoT systems, or are we training them to click buttons?

In many universities, IoT projects are still treated as extended embedded-system exercises.

Arduino.
ESP32.
Blink an LED.
Trigger a relay.

Nothing wrong with that.

But IoT is not just about making something move.

IoT is about data travelling.

From sensors.
Through networks.
Into platforms.
Across dashboards.
Into decisions.

If students never see that journey, they never really understand IoT.

The Chicken and Egg Problem Nobody Talks About

Let me share a frustration I rarely say out loud.

Favoriot is still new compared to global platforms.

Students don’t know us because there are fewer tutorials.
There are fewer projects online.
There are fewer YouTube videos.

And because of that, students don’t choose us.

Then I stop and think, how do you ever break this loop?

No users means no content.
No content means no discovery.
No discovery means no users.

Classic chicken and egg.

This is why I spend time going to universities.
Why I accept invitations to serve on industry advisory panels.
Why I keep introducing Favoriot in syllabus discussions.

Not because I want students to use Favoriot blindly.

But because someone has to be the first builder.

“But, Sir, Favoriot Has No Mobile App”

I hear this a lot.

And yes, for a long time, Favoriot did not have its own mobile app.

But here’s something many students don’t know.

There are MQTT mobile clients on Android and iOS.
They already have dashboards.
You configure them.
Connect to Favoriot.
And instantly see live data on your phone.

When I explain this, I see faces change.

“Oh… we didn’t know that.”

That sentence tells me everything.

Sometimes adoption is not about missing features.
It is about missing awareness.

And that is on us.
We need to explain better.
Show better.
Document better.

The Part Students Rarely See: The Full IoT Stack

This is where I get passionate.

IoT is not one skill.
It is many skills stacked together.

When students use platforms that hide everything, they only learn the top layer.

Here’s what real IoT demands.

Hardware
Sensors. Microcontrollers. Power. Battery life.

Connectivity
MQTT. CoAP. REST. WiFi. Cellular. LPWAN.

Platform
Device management. Ingestion. APIs. Storage.

Visualisation
Dashboards. Alerts. Rules.

Analytics
Understanding what happened. Why did it happen? What might happen next? What action to take?

Security
From device firmware to cloud access.

I sometimes ask myself, how can someone troubleshoot what they never learned existed?

Why I Don’t Believe in “No-Code IoT”

This may sound unpopular.

But I don’t believe IoT can be fully no-code.

IoT is physical.
It touches hardware.
It touches networks.
It touches real environments.

You need to understand flows.
You need to debug failures.
You need to trace where the data stops.

If there is no data on the dashboard, is it the platform’s fault?

Or is the sensor dead?
Is the firmware corrupted?
Is the network unstable?
Is the battery empty?

If everything is hidden, you don’t know where to look.

That’s dangerous.

PaaS Is Harder, and That’s the Point

Favoriot is closer to a platform than an app.

Some people say it’s harder.
They are right.

But difficulty is not a flaw.
It is a teacher.

When students use a platform that requires them to configure devices, protocols, dashboards, and rules, they are forced to think.

Why did I choose MQTT here?
Why is my data not arriving?
Why does this alert trigger late?

Those questions build engineers.
Not button-clickers.

Analytics Is Where IoT Becomes Meaningful

I always remind students.

Collecting data is not the goal.
Understanding data is.

IoT analytics moves in stages.

First, you look back.
What happened?

Then you ask why.
What caused it?

Then you look ahead.
What might happen next?

Finally, you decide.
What should I do about it?

This is why we built Favoriot Intelligence inside the platform.

Not as a separate system.
Not as an external tool.

One pipeline.
End-to-end.

Data comes in.
Insights come out.
Actions happen.

This is where IoT starts to feel alive.

AIoT and the Future Students Will Walk Into

Things are shifting fast.

AI is no longer optional.
Edge intelligence is becoming real.

Models trained in the cloud.
Inference pushed to devices.
Decisions made closer to reality.

Students who only learned drag-and-drop dashboards will struggle here.

Students who understand flows, stacks, and constraints will adapt.

That difference matters.

Why I Care So Much About This

People sometimes ask why I spend so much time with universities.

The answer is simple.

I have seen graduates enter the industry confused.
Overwhelmed.
Afraid of real systems.

I don’t want that.

I want students who can walk into a telco, a factory, a startup, or a smart city project and say,

“I don’t know this tool yet, but I understand how IoT works.”

That confidence changes careers.

Practical Tips for Students Learning IoT

Let me leave you with a few honest tips.

Learn beyond your demo
A working demo is not the finish line. Ask what breaks when conditions change.

Trace data end-to-end
Always ask where data starts and where it stops.

Understand at least one protocol deeply
MQTT, CoAP, or REST. Know how it behaves when networks fail.

Build dashboards yourself
Dragging widgets teaches more than screenshots.

Make something fail on purpose
Turn off WiFi. Drain the battery. Observe what happens.

Learn one platform properly
Not ten platforms shallowly.

Document your struggle
Others learn from your mistakes.

A Quiet Invitation

If you are a student reading this and you feel slightly uncomfortable right now, that’s good.

It means you are growing.

If you are a lecturer, consider whether your students are learning embedded systems or IoT.

And if you are one of the early builders willing to share your Favoriot project, you are not just building a system.

You are building a community.

Someone has to be first.

I hope you’ll be one of them.

I would love to hear your thoughts, your struggles, or your stories.
Leave a comment. Let’s talk.