Since day one, a hallmark of NativeScript development has been its focus on making native mobile app development accessible to web developers. We improved upon this by extending the framework with support for Angular and shortly thereafter with Vue.js. More recently, a focus has been on sharing code between web and mobile apps with both Angular- and Vue.js-based code sharing strategies.
Reusing skills and writing less code to cover more platforms is a clear priority. This includes making developers more productive with the skills and resources they have on-hand today. So it's high time that our developer tooling caught up!
Let me introduce you to a new low code tool from Progress for professional developers we call Kinvey Studio.
Looking for a quick way to learn more about Kinvey Studio? Watch the Kinvey Studio webinar now!
But first, let's take a quick trip down memory lane and examine just how we got to where we are today.
The truth is, "low code" or "no code" tooling has been around for years. Think back (way back) to the days of Netscape Communicator and its world-shattering combination of a web browser with an integrated WYSIWYG HTML editor!
Or what about Microsoft desktop developers who first got their feet wet with Visual Basic via a drag-and-drop canvas?
For many of us, low code tools started as a way to learn how to program. But problems arose when we realized the code generated by these tools was, let's just say, an utter disaster:
However, some tools like Adobe Dreamweaver worked with you, and not against you, leaving you with mostly human-readable (and editable) code. Providing the "roundtrip" capability to go from WYSIWYG visual design, to straight code, and back again, became a critical part of a real-world workflow.
Today though, app development needs are becoming more complex, with more screens needed across more distinct platforms. And today's definition of an "app" oftentimes means:
Along with increased complexity comes an increased need for tooling that can keep up with today's needs. This is where Kinvey Studio comes in.
If you're looking for an elevator pitch for Kinvey Studio, it goes something like this:
Let's break down that sentence:
With a name like "Kinvey Studio", it should be no surprise that the product itself relies on the mature foundations provided by the Progress Kinvey serverless backend. But Kinvey Studio goes far beyond the backend and builds upon on a variety of mature and performant libraries and frameworks. For instance:
You're going to hear A LOT more about Kinvey Studio in the coming weeks and months. In the meantime, if you'd like to know more, I suggest the following next steps: