# Appropriateness of Ignition, Vision and Perspective **URL:** \ **Category:** General Discussion\ **Tags:** perspective, vision\ **Created:** [January 19, 2024, 9:18pm UTC](https://forum.inductiveautomation.com/t/appropriateness-of-ignition-vision-and-perspective/84523 "2024-01-19T21:18:39Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 19, 2024, 10:05pm UTC](https://forum.inductiveautomation.com/t/appropriateness-of-ignition-vision-and-perspective/84523/2 "2024-01-19T22:05:02Z")
If you have prior experience with conventional HMIs and branded SCADA (Rockwell, Siemens, Aveva, etc.), you will get up to speed fastest if you develop in Vision. If you have specific things you want available on mobile, buy both Vision and Perspective licenses (I recommend this to all my clients) and do those tasks separately. Perspective does require more code than Vision, for a few reasons: - The historian and databases produce datasets that usually need transformation into web-friendly JSON. ("Usually" meaning "any time you want per-row styling", and sometimes more often than that.) - Perspective strictly isolates components in its views from components in other views, including nested or repeated views (the equivalent of Vision templates), requiring message passing architectures with code on both ends. Vision has no such restrictions. - Aside from datasets, there is an "impedance mismatch" between strictly-typed java objects, and loosely-typed JSON/javascript objects, which can require developer intervention to get the right results, particularly for date/time data types. You might find the various pros and cons discussed in this topic helpful: > [@Vision Vs Perspective Debate](https://forum.inductiveautomation.com/t/vision-vs-perspective-debate/81849): > > I have been getting to grips with Ignition for a while now and have developed some User Interfaces for Data Collection and Analysis. I am leaning heavily towards Perspective but Vision has been in use at my company for a couple of years in a different department, where they work with machine data largely. I will be the first person in my department to use Ignition, I work with a mixture of numerical and categorical data from users. I prefer everything about Perspective (usability, visibility et… Other topics linked within that one may be helpful, too. --- _[View the full topic](https://forum.inductiveautomation.com/t/appropriateness-of-ignition-vision-and-perspective/84523)._