Lightswitch & the HTML Client - What Does This Mean?
Join the DZone community and get the full member experience.Join For Free
for you to understand the rest of this post it is vital you have a high level understanding of lightswitch and how it works. lightswitch is a rapid development platform from microsoft that makes development of line of business (lob) apps really easy. the team at microsoft often talk about citizen developers – i.e. people who are not full time developers, but are the “it guy” in the department or company that need to put together a great looking solution. the team also talk about no-code solutions – where you can build great systems without code.
both statements from the team are true and false at the same time. sure your accountant can build a crm system with no code in lightswitch, but lightswitches true value is that it is a professional development tool, and in reality unless it is a really simple solution you will need a touch of code.
what is great is that lightswitch allows the citizen developer to write a system that can be matured by professional developers later on – it’s power is that it does not lock you into being too simple or too complex a development system.
for me the value proposition is that you get real rapid development, that citizen developers can put together and extend solutions that are well architected and that when the need is there a professional developer can extend that solution and hand it back over to the citizen developer – it is the circle of lightswitch.
when you craft a (avoiding the development term here on purpose) lightswitch create a multi-tier architecture, that is either two tier (client & database) or three tier (client, server & database). two tier is really three tier but the server & client are just one package.
the database can be any support by lightswitch, the middle tier is odata and the front end is silverlight. the choice of front end has recently hurt lightswitch because silverlight is dying . however if you step back for a second and think about it lightswitch provides the easiest and fastest way to build a complete (and i mean complete, authentication, methods, proper designed) odata solution… you could always ignore the client portion and build on top of the odata server.
making a html client
the html client mode for lightswitch is a recently announced new feature that allows you to build a client that runs in a browser, and not just internet explorer on windows (dynamics crm i am looking at your shameful behaviour) but pretty much any browser, say on an ipad:
this is possible because of two things, the odata server which allows really any technology to connect to it, and the second piece of the lightswitch system the lsml file.
i hope you have never heard of the lsml file, as it is not a nice place to go to – it is a massive (even simple demo’s i build are thousands of lines) xml file that stores all of the lightswitch system in a “lightswitch domain language”. this enables the team to take that information, parse it and produce output based on it. so the concept of producing a parser that creates html rather than silverlight is really simple… just build the parser.
what do we know about this html client so far?
it is early days, in fact there are no bits available yet, but we do know some things from the demo’s and screen shots that are available.
- multiple themes will be supported (their is a dark & a light at least) – thanks to the jquery mobile that powers it.
- it is a separate client – so you will have a silverlight experience and then also have the html experience added in.
the important two issues
to wrap this up it is a very exciting point in time for the lightswitch world with so much happening that i think it is important to take a step back and find a few key aspects about this amazing feature that will help position it. there are two that really stand out to me from all the announcements:
this is not a silverlight to html generator – it is separate. this means that awesome silverlight chart you use today will not magically work in the html client. this has both advantages and disadvantages, but if you think about the dying of silverlight i am very glad that they have a whole new growth path.
it also allows for the real scenario of supporting a rich experience in silverlight in a company (where we control all the machines and know we can run silverlight for a long time still) and having a mobile or companion experience in html for those people on the road. sure they do not get the great sales forecast chart but they can still capture their sales on their ipad.
a recent did an survey of app developers looked at what they are building today, what they were building and what they intend to build in the future (future = one year in this survey). interestingly there are only two platforms that are getting growth in the future? html & windows phone. android, iphone and many others are all expected to decline.
if you think about those numbers and add in the massive investments in html development that are in windows 8, it should not surprise you that web development is a major area in the future of all developers. it also means that web developers can start to have way more opportunities in the market outside of building websites & portals, and that is very exciting as that little garage web designer company today could be a major line of business developer in a few years.
Opinions expressed by DZone contributors are their own.