We offer a fast path to
implementing user-friendly phone and tablet views – without requiring a responsive design
rewrite – that will enable your in-house staff to get you to mobile, in likely the most
concise way possible. Testing is easier and more straight-forward too.
If you provide your name and email address below, we'll send you prices along with links to 4 working versions of this package.
Watch - Play Promo - Contrasting the base responsive (with bootstrap) Visual Studio Web Forms web application project home page with the Mobile ASPX alternative.
So the difference then, behind the scenes, is that content pages (using Mobile ASPX), can achieve 4 pleasing views without requiring any use of responsive technique.
Surprisingly, the Mobile ASPX alternative actually looks better in several of the views and also when resizing during desktop view.
Please note that there are several project templates in Mobile ASPX that don't use responsive techniques at all, even in the menu or master page area.
The Mobile ASPX product provides for 4 optimized views – mobile, tablet, desktop and theatre, chiefly via HTML5. By standardizing to just 4 views,
where each view uses essentially the same XHTML, our product helps you strike a consistent balance between device width, pixel scaling and user control and to do it in less time. For example, the Desktop view allows runtime width adjustment of the content in the device window where as the mobile views do not,
thus enabling the mobile device user with a more consistent zoom instead. Testing scenarios also become simpler
and more deterministic.
If you don't have staff that is available or
knowledgeable about the programming behind your ASPX web pages, we are able to provide the technical
service that is needed to get to implementation. But really, the OO programming part that comes with the product is
Mobile ASPX includes licensed c# source code methods that developers insert
into the code-behind of pre-existing master page(s), such as those oriented towards desktop-sized presentation. Before mobile browsers, it was generally accepted technique to use a mimimal amount of master pages, taking advantage of the OO flexibility in the code-behind to create just one master page per style. Mobile ASPX needs just 1 master page per style to help you deliver the 4 views.
Similarly, a single master page can be used even if there are multiple directory levels in the website.
VB.NET source code versions are available (OK, yeah we
converted them from c# using a tool).
Actually there are 3 project structures provided in the product (for both c# and vb.net). Each is built upon a different Visual Studio base project standard template starting point. We provide these to
make it easy to isolate the changes you need to make to your existing works. Similarly, in making
the product easy to work with, all of the CSS and XHTML and OO code included with Mobile ASPX is virtually identical
or conceptually identical across project structures.
One more very important point, we think that Mobile ASPX is, in all liklihood, compatible with any responsive design techniques you already have in place. We demonstrate this in the Project1 template. Link to
(rather technical) details on project templates and their differences... We are all about compatibility with this product!
We think our code package can help you deliver mobile formats on your custom
web and intranet web forms - fast. For the complete announcement text on Mobile ASPX TechCrystals Code Package, please visit our News and Events page Announcing Mobile ASPX TechCrystals Code Package!
For confidential pricing info, license agreement and master page method names and links – contact us today!
(we will not rent, sell or share this information)
(your name and a valid email address is required)