Every semester, I meet students who proudly show me their IoT projects. Some build smart dustbins. Some build flood monitoring prototypes. Some build temperature monitoring systems for cold-chain delivery. Some build smart parking models using cardboard, wires, sensors, and a lot of hope.
I always enjoy those moments because they remind me of why technology education is so powerful. There is something special about watching a student connect a sensor, upload data to the cloud, and suddenly realise, “Eh, I can actually build something useful.”
But there is one question I always ask.
“What IoT platform are you using?”
Most of the time, the answers are almost the same.
Blynk.
ThingSpeak.
Sometimes Firebase.
Sometimes a custom dashboard built in a hurry the night before presentation day.
I smile. Not because those platforms are wrong. They are not. In fact, they have helped many students start their IoT projects. But I also feel a small discomfort because the question is bigger than the platform name.
Is the student learning IoT as a complete system, or only learning how to make a project look alive for demo day?
That is where the real conversation begins.
For universities, choosing the right IoT platform is not only about which platform is free, popular, or easy to connect with Arduino. It is about what kind of graduates we want to produce. Do we want students who can display sensor readings on a graph, or do we want students who understand how real IoT systems collect data, manage devices, trigger alerts, support decisions, and grow beyond the classroom?
That is why the question “Which IoT platform is best for students?” deserves a practical answer.
Easy Is Good, But Too Easy Can Become a Trap
Let me say this carefully. Easy platforms are helpful, especially for beginners. When students are just starting, they need confidence. They need to see results quickly. If the first IoT experience becomes too painful, they may give up before they even understand the power of connected devices.
No lecturer wants to spend three weeks helping students debug Wi-Fi passwords, missing libraries, wrong ports, incorrect tokens, and mysterious error messages that seem to appear only at 2 a.m.
So yes, an easy learning curve matters.
But I also believe that if the platform only teaches the easiest path, students may never understand the deeper structure of IoT. They may know how to connect a sensor, but they may not know what happens after the data arrives in the cloud.
A proper IoT learning experience should expose students to the full flow of an IoT system:
- Device connectivity
- Data upload
- Data storage
- Dashboard design
- Alerts and rules
- APIs
- User access
- Security awareness
- Analytics
- Real-world use cases
When I look at student projects, I do not only look at whether the sensor works. I look at whether the student understands the purpose of the data.
What will you do with this data?
Who needs to see it?
When should the system alert someone?
Can this project survive outside the lab?
That is where many student projects become weak. They are good prototypes, but they are not always ready to become useful solutions.
“Students should not learn IoT only to pass a subject. They should learn IoT to solve problems they can see, touch, and understand.”
Dr. Mazlan Abbas
The Five Things Universities Should Look For
If a university wants to choose an IoT platform for students, I suggest looking at five practical areas. These are not complicated criteria, but they can make a big difference in how students learn and how lecturers teach.
1. Learning Curve
Students need a platform that does not frighten them on the first day. A student-friendly IoT platform must allow them to connect common devices such as ESP32, ESP8266, Arduino, Raspberry Pi, or industrial gateways without needing months of technical preparation.
The learning curve should be gentle at the beginning, but it should not remain too shallow forever. Students should be able to start with basic data upload, then gradually move into dashboards, APIs, alerts, analytics, and deployment thinking.
This is one reason platforms like Blynk and ThingSpeak became popular. They are easy to start. Tutorials are everywhere. Many students can follow YouTube videos and get something working within a few hours.
That is useful, especially for first exposure.
But universities should ask a second question.
After students learn the basics, where do they go next?
If the platform becomes too limited after the first prototype, students may hit a ceiling. They may know how to make a nice demo, but they may not learn how to design a proper IoT system.
For universities, the best platform should support both beginner learning and advanced learning. It should help students start simple, then grow deeper.
2. Project Readiness
A final year project should not feel like a toy. I know that sounds a bit harsh, but I have seen many projects where the idea is strong, yet the platform choice makes the project look small.
Imagine a student builds a flood monitoring system. The sensors work. The dashboard shows water levels. The graph looks nice. Then I ask a few practical questions.
Can the system alert the local council?
Can it support multiple locations?
Can it store historical data?
Can another user log in and monitor only one area?
Can the system be expanded into a city-level monitoring system?
Usually, the student pauses.
That pause tells me something. The student was taught how to connect devices, but not always how to think about real deployment.
A good IoT platform for students must help them move from prototype to project readiness. It should support features that resemble real-world IoT systems, not just simple charts.
These include:
- Multiple devices
- Multiple data streams
- User access control
- Event-based alerts
- API connectivity
- Data history
- Dashboard sharing
- Application-level use cases
This is where I see strong value in FAVORIOT for universities. FAVORIOT is not only a place for students to test sensors. It can help them build use cases that look closer to industry needs.
A student building a smart agriculture project should not stop at soil moisture graphs. The project should show irrigation alerts, crop condition trends, farm dashboards, and possible decisions.
A student building a smart building project should not stop at temperature and humidity readings. The project should show comfort levels, abnormal readings, equipment behaviour, and suggested actions.
That is real learning.
3. Local Support
This is the part many universities forget.
When a platform is based overseas, the tutorials may be good, but the support is usually generic. If a student faces a problem, they search forums, Reddit, YouTube, GitHub, or old blog posts. Sometimes they find the answer. Sometimes they get trapped in a maze of outdated libraries, broken links, and comments from 2017.
I have seen students spend days trying to fix small issues that could have been solved quickly with proper local guidance.
This is where local support becomes a serious advantage.
For Malaysian universities, having access to a local IoT platform means lecturers and students can ask questions, request training, discuss use cases, and get guidance in a context they understand.
Malaysia has its own education environment. We have our own final year project culture, our own industry needs, our own smart city challenges, and our own local problems that students can solve.
An IoT platform for Malaysian students should not only teach global examples. It should also expose them to local problems such as:
- Flood monitoring
- Cold-chain logistics
- Campus energy monitoring
- Smart agriculture
- Vehicle tracking
- Water quality monitoring
- Smart city dashboards
- Industrial machine monitoring
These are not imaginary textbook problems. These are problems students can see around them.
When support is local, the conversation becomes easier. A lecturer can say, “I want my students to build a smart campus project.” A student can ask, “How do I send ESP32 data to the platform?” A university can plan, “Can we train 50 students in one workshop?”
That kind of closeness matters.
“A local platform is not just about geography. It is about understanding the problems our students are trying to solve.”
Dr. Mazlan Abbas
4. Tutorials and Teaching Materials
Students love tutorials. Lecturers love tutorials even more because nobody wants to rebuild the same lesson from scratch every semester.
A good IoT platform for universities must have step-by-step materials that students can follow. The documentation should not only be written for professional developers. It should also guide beginners from zero to a working project.
Useful teaching materials should include:
- Device setup
- Coding examples
- Platform account setup
- Data upload steps
- Dashboard creation
- Alert configuration
- Common errors
- Sample use cases
- Project ideas
- Extension tasks for advanced students
The best tutorials do not only show students what to click. They explain why each step matters.
This is important because IoT is not only a technical subject. It is a systems-thinking subject. When students learn IoT properly, they begin to understand the relationship between physical devices, networks, cloud platforms, data, people, and decisions.
A tutorial should not only say, “Copy this code.”
It should make students think.
Why do we collect this data?
How often should the device send data?
What happens if the network fails?
Who owns the data?
How secure is the device?
These questions are becoming more important, especially when IoT devices are connected to buildings, cities, factories, farms, and public infrastructure. Students should learn this early, not after they graduate.
5. Showcase Value
Universities need platforms that help students showcase their work clearly and professionally. This may sound like a small thing, but it is not.
A student project with a messy dashboard can make a good idea look weak. A student project with a clean dashboard, proper data flow, alerts, use-case explanation, and a working demo can impress panels, industry partners, and potential employers.
The platform should help students explain their project in a way that makes sense.
Not only:
“This is my sensor.”
But also:
- This is the problem.
- This is the data I collect.
- This is how the platform receives it.
- This is the dashboard.
- This is the alert.
- This is the decision that can be made.
- This is how it can be expanded.
That is the difference between a lab experiment and an industry-ready concept.
For universities, showcase value is important because good student projects can become competition entries, research prototypes, industry collaboration demos, grant proposal examples, teaching lab assets, open-day exhibits, or even startup ideas.
A good IoT platform should help students tell the story behind the data.
Comparing Common IoT Platforms for Students
Let us look at the platforms students often use and where each one fits.
Blynk
Blynk is popular because it is beginner-friendly. Students can create mobile dashboards quickly and connect devices without too much difficulty. For early learning, it works well.
Its strength is simplicity.
Its weakness is that students may become too focused on app display rather than full IoT architecture. It is good for quick prototypes, but universities may need something broader when teaching project readiness, multi-user systems, local industry use cases, and longer-term data thinking.
ThingSpeak
ThingSpeak is also popular in universities. It is useful for basic sensor data logging and graphing. Many students use it because tutorials are easy to find.
Its strength is simple data visualisation.
Its weakness is that students may treat IoT as “sensor plus graph.” That is only one piece of the puzzle. For deeper learning, students need more exposure to alerts, roles, APIs, dashboards, application context, and deployment design.
Firebase
Firebase is powerful for app developers. Students who build mobile apps may find it useful for storing and syncing data.
Its strength is app development support.
Its weakness is that it is not an IoT-specific platform by default. Students may need to build many IoT-related features themselves. This can be useful for advanced software students, but challenging for beginners who are still learning sensors, networks, and data formats.
ThingsBoard
ThingsBoard is a strong open-source IoT platform with many features. It can be useful for advanced students and lecturers who want control and flexibility.
Its strength is depth.
Its weakness is setup and maintenance. Universities need technical confidence to install, configure, teach, and support it. For some classes, that may be too heavy. For postgraduate or advanced labs, it can be a good option.
FAVORIOT
FAVORIOT sits in a practical position for Malaysian universities. It gives students a platform that can be used for learning, prototyping, dashboards, alerts, APIs, and real use-case development. It is also local, which means the support, training, examples, and industry context can be closer to what Malaysian students and lecturers need.
Its strength is the balance between learning and project readiness.
Students can start with basic data uploads, then grow into stronger projects that reflect real use cases. Lecturers can use it for teaching. Universities can use it for labs, workshops, competitions, and industry collaboration.
For students, the platform becomes more than a place to display data. It becomes a place to understand the flow from device to decision.
That is the real lesson.
Why FAVORIOT Makes Sense for Universities
I do not believe universities should choose an IoT platform only because it is local. That is not a strong enough reason. A platform must earn its place in the classroom by being useful, practical, teachable, and relevant.
This is where I believe FAVORIOT can contribute.
1. It Helps Students Learn the Full IoT Flow
Students can understand how devices send data to the cloud, how data is stored, how dashboards are created, and how alerts can be triggered.
This teaches IoT as a complete system, not as a loose collection of sensors.
2. It Supports Real Project Ideas
FAVORIOT can support many student project themes, including:
- Smart agriculture
- Smart campus
- Smart building
- Smart city
- Flood monitoring
- Cold-chain monitoring
- Vehicle monitoring
- Environmental monitoring
- Energy monitoring
- Industrial machine monitoring
This gives lecturers flexibility across engineering, computing, data science, agriculture, and business faculties.
3. It Gives Local Relevance
Students can build projects that solve problems they see in Malaysia. That makes learning more meaningful.
A student in Kelantan can build a flood alert project. A student in Johor can build a smart factory monitoring project. A student in Selangor can build a campus energy dashboard. A student in Sabah can build a remote environmental monitoring system.
The platform becomes a bridge between classroom learning and local problem-solving.
4. It Can Support Training and Workshops
Universities often need structured learning sessions. FAVORIOT can support this through training, tutorials, and guided project development. This is helpful for lecturers who want their students to move faster without spending too much time solving repeated technical issues.
When students receive proper guidance, they can focus on the project idea, data logic, and outcome.
Of course, wiring errors will still happen. Somewhere in every IoT lab, one jumper wire is always guilty. That is part of the learning experience.
5. It Helps Students Think Like Problem-Solvers
This is the most important part.
IoT is not about gadgets. IoT is about solving problems using connected data.
When students use a platform that supports dashboards, alerts, analytics, and real use cases, they begin to ask better questions.
Not only, “Can my sensor work?”
But, “What decision can this data support?”
That is the shift universities should encourage.
“The best student project is not the one with the most sensors. It is the one that helps someone make a better decision.”
Dr. Mazlan Abbas
So, Which IoT Platform Is Best for Students?
The honest answer is that it depends on the learning goal.
If the goal is to introduce very basic IoT in one lab session, Blynk or ThingSpeak may be enough. If the goal is app development with some connected data, Firebase may be suitable. If the goal is advanced open-source platform control, ThingsBoard can be useful.
But if the goal is to help students build IoT projects that are easier to teach, locally supported, project-ready, and closer to real-world use cases, then FAVORIOT deserves serious attention from Malaysian universities.
Not because it is local only, but because it helps students move from “my sensor sends data” to “my project can support decisions.”
That is the difference.
Universities Should Stop Teaching IoT as a Demo-Only Subject
This is my concern. Too many students treat IoT as a final year project checkbox.
Buy sensor.
Connect microcontroller.
Send data.
Show graph.
Present.
Graduate.
Then what?
The world does not need more abandoned prototypes sitting inside lab cupboards. The world needs graduates who can design connected systems that work outside the classroom.
Universities have a huge role to play here. They can choose platforms that stretch students a little further. Not too much until they drown, but enough to make them stronger.
A good IoT platform should teach students how to think about reliability, security, data quality, user needs, deployment, maintenance, alerts, decisions, business value, and social impact.
That is how we prepare students for the real world.
My Final Thought
When a student builds an IoT project, I do not want them to say only, “My dashboard can show temperature.”
I want them to say, “My system can help a cold-chain operator detect temperature problems before goods are damaged.”
I want them to say, “My system can help a campus reduce energy waste.”
I want them to say, “My system can help farmers monitor soil conditions.”
I want them to say, “My system can help local councils respond faster to floods.”
That is when IoT becomes meaningful. That is when a student project becomes a story of impact.
So, which IoT platform is best for students?
The best platform is the one that helps them learn fast, build properly, get support, showcase confidently, and think beyond the demo.
For many universities in Malaysia, I believe FAVORIOT can be that platform. It gives students a practical path from classroom learning to real-world IoT thinking.
And maybe the next great smart city, smart agriculture, or smart campus idea will not come from a giant corporation. Maybe it will come from a student who started with one sensor, one platform, one dashboard, and one simple question.
What if this small project can solve a real problem?
That is the kind of question worth building for.
What do you think? Should universities continue using the usual IoT platforms, or is it time to introduce students to more locally relevant and project-ready platforms like FAVORIOT? I would love to hear your thoughts in the comments.
Discover more from Dr. Mazlan Abbas
Subscribe to get the latest posts sent to your email.
