The day 2 keynote this year is focused on things that are yet to come. Traditionally, the first day keynote intermingled the “what’s available now” stuff with the “what’s coming in the next 6, 12, 18, n” months. By breaking these things up into 2 days, it is a little more clear that what is shown today isn’t readily available, but is more of the direction of Citrix. Continue reading “Citrix Synergy 2015 Day 2 Keynote Live Blog”
Mobility is so ubiquitous that it is almost not even a separate thing anymore. I have had some experience building mobile apps and wanted to ponder some self-proclaimed theorems which are outlined in this article.
Mobility is so ubiquitous that it is almost not even a separate thing anymore. This creates a challenge for enterprises that offer BYOD mobile devices and corporate data access. How do you enable the mobile workforce with enterprise applications? One way is to roll your own mobile application to get the necessary data into the mobile user’s hands. I have had some experience with this and wanted to ponder some self-proclaimed theorems which are outlined below.
Mobile applications developed for native devices with native code are superior.
The following is an example of what you might need to build native mobile applications for various mobile devices:
Android SDK, Android NDK
Eclipse, NetBeans, IntelliJ IDEA
C# and others
Window 8 Metro Style Apps
Java ME + Optional Packages + API extensions
Unfortunately, BYOD makes Theorem #1 hard. If you are going to go the native code route, you have to maintain a separate code base (with separate IDE’s) for all possible devices your users will bring in. There are some other frameworks that I’ll talk about in another article that help with this, but there is always a tradeoff.
Apps that Look Better are Perceived to be Better.
Looks matter. Period. If you give an application to a user that has limited functionality but looks sexy, that application will be perceived as better than an application that has more functionality but is ugly. You know it’s true.
Therefore, do yourself a favor and use a framework like one of the following:
These frameworks make it easy to make it look like you know what you are doing (at lease design-wise)
Inverse Proportions are Everywhere.
There is always a tradeoff somewhere. Referencing the picture above, think about painting a room. I can paint a room with a paintbrush and not waste too much paint. However, to speed things up, I use a paint roller and waste more paint. Therefore, the ease/speed in which I paint a room is inversely proportional to how much paint I waste.
The same thing is true for security. If everyone in the world had a public IP address with wide open ports, things would be pretty easy if there were not bad guys/girls out here. In the real world, there are bad guys/girls out there, so we have to attempt to keep them out. The security measures can be a burden on the user. Therefore, security is inversely proportional to usability.
There, of course, is a tradeoff. Building mobile apps with abstraction layers like PhoneGap introduce translation. You may not have access to all mobile device features immediately, there can be a performance tax, and apps will tend to be bigger. Not all mobile frameworks are created equal and I will talk about some pros and cons of different frameworks (like Xamarin, Citrix Mobile SDK for Windows Apps, Intel XDK, etc.) in a separate article.
So, there you have it. My self-proclaimed theorems for mobile app development. Agree? Disagree? Or, have something else to add? Just leave a comment below.
Citrix Synergy is back in Anaheim, California this year and I will be live-blogging the keynote. You can watch the keynote live at CitrixSynergy.com as well. I am sure there will be a focus on mobility, but with the release of XenDesktop and XenApp 7.5, I am excited to see Citrix getting back to the future (again).
Your end users expect mobile access to enterprise resources now. Unfortunately, our traditional remote access methods do not lend themselves easily to mobile form factors. So, we are left with the choice to use 3rd party apps, “mobilize” existing apps, or build our own. This article will address one of the players aimed at helping you build your own mobile apps with less effort.
Mobile Enterprise Apps – Virtualize, Buy, or Build?
When it comes to mobile enterprise applications, you basically have 3 choices:
Virtualize what you have (via Citrix HDX, RDP, VMware PCoIP, etc.)
Buy something from a 3rd party
Build something yourself
There are use cases for each of these, but I’m going to focus on one way to build something yourself. In this case, I’m going to cover PhoneGap.
What is PhoneGap?
What’s needed to develop with PhoneGap?
You still need to use the various platform IDE’s to develop an app with PhoneGap. For instance, I developed a simple app for iPhone and Android. For iPhone, I used Xcode to create and compile the PhoneGap application. For Android, I used Eclipse to create and compile the application. I had to set up each IDE to use the PhoneGap framework, but that is all documented pretty well.
I started with Xcode and got things working liked I wanted for iPhone. Then, I literally just copied and pasted my HTML, CSS, and images over to Eclipse and the Android app just worked. My app is very simple, but here are the results:
What is the catch?
PhoneGap is free. Even though Adobe acquired PhoneGap in 2011, the PhoneGap code was contributed to the Apache Software Foundation (ASF) under the name Apache Cordova and graduated to top-level project status in October 2012.
I have noticed that some PhoneGap apps seem to run a little sluggish when dealing with animations as compared to traditional apps. I’m assuming this is due to the chrome-less browser nature of PhoneGap applications. However, when dealing with enterprise applications, I do not see this as being a big issue.
The other issue I see for enterprises (and this is not unique to PhoneGap) is data access. Your application is really just another front end for data. You have to provide enterprise data access somehow. This can be done via VPN, or using local device storage and sync strategies. Like I said, this isn’t unique to PhoneGap, but it is something to think about.
On the contrast, you are not developing “real native” code and devices may come out with features faster than the PhoneGap framework can accommodate. You still have a data problem. If your app requires a lot of fancy animated graphics, then PhoneGap may or may not suit your needs.
So, there you go. If you have experience with PhoneGap or just something to add, feel free to leave a comment below.
Citrix Synergy is in Anaheim, California this year. With the recent release of Excalibur, it will be interesting to see what is revealed during the keynote. I’ll be live-blogging the keynote this year. Check it out here or on Twitter @JasonConger.
It is time for Citrix Synergy, and I will be live-blogging the keynote. With the recent release of Excalibur, I expect the keynote focus to be a lot around capabilities and features. I also expect to see some more around mobility, networking, and cloud. Be sure to stay tuned here and/or follow me on Twitter.
In the previous version, the responsive design code only kicked in on session initiation (i.e. logon) – meaning if you started a session on a fat client and then reconnected to the session on a mobile device, then the fat client display would show up on the mobile device. We don’t want that. So, by catching the reconnection event, we can re-style the app at any point (session initiation or reconnection). Start the application on a fat client and then reconnect via a mobile device and the mobile style will kick in (and vice versa).
Here’s the bit of code to take care of it (if you don’t care about the code and just want to skip to the download, just follow this link):
private static extern bool WTSRegisterSessionNotification(IntPtr hWnd, [MarshalAs(UnmanagedType.U4)]int dwFlags);
private static extern bool WTSUnRegisterSessionNotification(IntPtr hWnd);
private const int NOTIFY_FOR_THIS_SESSION = 0;
private const int WM_WTSSESSION_CHANGE = 0x2b1;
private const int WTS_REMOTE_CONNECT = 0x3;
private const int WTS_REMOTE_DISCONNECT = 0x4;
private bool registered = false;
protected override void OnHandleDestroyed(EventArgs e)
// unregister the handle before it gets destroyed
protected override void OnHandleCreated(EventArgs e)
registered = WTSRegisterSessionNotification(Handle, NOTIFY_FOR_THIS_SESSION);
protected override void WndProc(ref Message m)
if (m.Msg == WM_WTSSESSION_CHANGE)
if (m.WParam.ToInt32() == WTS_REMOTE_CONNECT)
// The session is in the reconnect state, so style the app for the new session
if (m.WParam.ToInt32() == WTS_REMOTE_DISCONNECT)
// The session is in the disconnect state, so close the CMP if it is open
if (this.cmp != null && this.cmp.IsChannelOpen())
Try It Out Yourself
Want to try it out yourself? I have made the program and the source available so you can beat it up and come up with some more ideas. You can download it here.
Responsive Design that web developers use can now be applied to Enterprise Applications thanks to the Citrix Mobile SDK. This post will give you a glimpse of what is possible to get your wheels turning.
Have you heard of Responsive Web Design? The term was coined by Ethan Marcotte in his article on A List Apart. The gist of the idea is that web pages can be designed to adapt or respond to the entity that is viewing it. The Boston Globe’s website is a good example of responsive design. You can see by the screenshots below, that given enough screen real estate, the website has a 3 column layout. But, as the screen width starts to shrink, the layout is adjusted to 2 columns and then 1 column. Also, the navigation changes to better suit the layout and images are adjusted or hidden.
Applying Responsive Design to Enterprise Applications
Just like web pages, enterprise applications are starting to get viewed on a myriad of devices. What if we could take some of the same techniques web designers are using and apply that to enterprise applications? Well, as it turns out, we can with the help of the Citrix XenApp 6.5 Mobile Application SDK. By using the Mobile Application SDK, enterprise applications that are hosted on a XenApp 6.5 server can respond to the type of device using the application.
Responsive Application Example
As an example, I wrote an application that takes data from EdgeSight about the types of Citrix clients used in an environment. The application displays this information in a chart as well as a table. I then published this application from AppCenter on a XenApp 6.5 server and launched it using a fat client. You will notice that both the chart and the data table are shown as well as a menu strip at the top to select a chart type.
Now, if you launch the exact same application from the exact same server using a mobile device, some very interesting things happen:
Only the chart is shown initially. If you rotate the device, only the data table is shown.
The application’s window chrome is gone.
The width and the height of the application were changed to the width and height of the device.
Tapping the chart image brings up the device’s native picker.
Changing the orientation of the device changes the display.
Check out this short video for a demo:
Try It Out Yourself
Want to try it out yourself? I have made the program and the source available so you can beat it up and come up with some more ideas. You can download it here.
In this post, we will go over the installation steps of the Citrix XenApp 6.5 Mobile Application SDK, explorer what is added to the XenApp 6.5 server during installation, and compile one of the samples given in the SDK.
Now that we have setting up an Android emulator out of the way, let’s take a look at installing the Citrix XenApp 6.5 Mobile Application SDK and what the install does to a XenApp 6.5 server.
There are 2 parts that you need in order to develop applications that utilize mobile capabilities on a XenApp 6.5 server:
When you install the Mobility Pack, 2 new services are added to your XenApp server:
Citrix Location and Sensor Virtual Channel Service – this service enables a server side application to leverage Location and Sensor capabilities.
Citrix Mobile Receiver Virtual Channel Service – this service enables a server side application to use mobile device capabilities.
These 2 virtual channels are kept separate for security reasons. Maybe you want to have mobile device capabilities available, but you cannot enable GPS features due to security compliance. Location services are disabled on the Citrix Receiver by default. The way to enable the location capabilities is via Citrix policies. In order to use these policies, you will need to install the Citrix Group Policy Client-Side Extensions. These extensions are part of the XenApp Mobility Pack .zip file.
This policy is located under ICA\Client Sensors\Location. Notice that by default, location is disabled.
Citrix XenApp 6.5 Mobile Application SDK
So, the requirements for the Citrix XenApp 6.5 Mobile Application SDK state that you need Windows 7 64 bit (and the MSI is even named XenApp65MobileApplicationSdk64), but it installs to ..\Program Files (x86)\Citrix\MobilitySDK\. I tried installing the SDK on a Windows 7 32 bit system as well and it worked, so I’m not sure if something absolutely will not work on 32 bit.
I’m using Visual Studio for the examples. It appears that Visual Studio Express (free) will work as well, but I haven’t tested that myself.
Anyway, the documentation that comes with the SDK is pretty comprehensive so I’m not going to rehash it here. Since I will be showing you some of the examples using .Net, I do want to point out that you will need to run one of the following commands on your development machine in order for things to work:
Notice that there is a 32 bit or a 64 bit DLL register. So again, not sure why Windows 7 64bit is a requirement for development. Anyway, make sure you run the appropriate command above as administrator, otherwise you may receive an error stating “The module was loaded but the call to DllRegisterServer failed with error code 0x80070005” (which is a permissions error).
The final part of this article will focus on compiling and using the examples that come with the SDK. The one I’m going to point out here is the picker example. This example uses the native device’s UI to display a list of options. The example is actually a console application that has no graphics, so it is actually using the local device’s display mechanisms rather than trying to do some trickery on the XenApp server side. So, here we go…
Browse to \Program Files (x86)\Citrix\MobilitySDK\samples\native\showpicker
Double click on showpicker.sln to open the solution in Visual Studio
Build the solution by pressing F6
This will create an executable in \Program Files (x86)\Citrix\MobilitySDK\samples\native\Win32\Debug\showpicker.exe
Copy this showpicker.exe to your XenApp 6.5 server (I copied mine to \Program Files (x86)\Mobility\picker\showpicker.exe)
Publish the application via Citrix AppCenter
Launch the published application using an Android device (or emulator) with the latest Citrix Receiver installed.
NOTE: You may receive an error message that states “The program can’t start because MSVCR100D.dll is missing from your computer…” Here’s why – the solution was built in debug mode. Thus, debug DLL’s (notice the “D” in the DLL name) need to be on the XenApp 6.5 server. Here is what you can do:
From: \Program Files (x86)\Microsoft Visual Studio 10.0\VC\redist\Debug_NonRedist\x86\Microsoft.VC100.DebugCRT\msvcr100d.dll on your development machine
To: \Windows\SysWOW64\msvcr100d.dll on your XenApp 6.5 server
You could technically build the solution in Release mode instead of Debug mode and be okay, but to perform remote debugging, you will want to have the debug DLL on your remote machine. Speaking of debugging, here are 2 great write-ups on how to debug the mobile applications:
Once you pick one of the colors, the console application will give you feedback on the chosen item. When the appropriate receiver is available for iOS, then the native iOS selector would be shown with no code changes on the developer’s part. That is pretty cool!
In the next article on this topic, I will show you how to use mobile device orientation to change what is displayed to an end user. The example will include data and graphics. Stay tuned…
One of the coolest SDKs I’ve seen come out in quite a while is the Citrix XenApp 6.5 Mobile Application SDK. As of this writing, only the Android version of the Citrix Receiver is supported so I will show you how to set up an Android emulator with the Citrix Receiver for testing purposes.
One of the coolest SDKs I’ve seen come out in quite a while is the Citrix XenApp 6.5 Mobile Application SDK. Citrix defines the XenApp 6.5 Mobile Application SDK as “… a rich tool kit for developers to write touch-friendly, mobilized applications that are hosted on Citrix XenApp and delivered to any device with Citrix Receiver. These mobilized applications are able to leverage a wide set of mobile device functionality including GPS, sensors, cameras, and device buttons in the same way that locally running, native applications do.”
As of this writing, only the Android version of the Citrix Receiver is supported (iOS is on the way). Since I do not own any Android devices and I was anxious to get started, I had to set up an emulator and install the Citrix Receiver to get going with the SDK. Here is how I did it.
Install the Android SDK
Go to the Android SDK download page (http://developer.android.com/sdk/index.html) and pick the correct installer for your platform. I’m using Windows, so I chose the .exe installer file. After you run this .exe, you still do not have the emulator. The reason for this is the Android SDK archive initially contains only the basic SDK tools. It does not contain an Android platform or any third-party libraries. You must install the Platform-tools and at least one version of the Android platform using the SDK Manager.
I installed the Android SDK Platform-tools and all options for Android 4.0.3.
After the install completes, be sure to add %ProgramFiles%\Android\android-sdk\platform-tools to your PATH environment variable. This will be handy later for installing the Citrix Receiver.
Create an Android Virtual Device
After the installs complete, you can launch Android Virtual Device Manager (AVD Manager). This can be found in the Windows start menu under Android SDK Tools \ AVD Manager. AVD Manager is used to create various virtual devices running the Android OS.
As you can see, I created an Android 4.0.3 device with 100 MiB of local storage. The more storage you add to your AVD, the longer it will take to boot. Since this AVD is only being used for XenApp 6.5 testing, I only allocated 100 MiB. The first boot of your AVD will take a little longer than subsequent boots.
Download the Citrix Receiver for Android
Now that we have a functioning Android emulator, we need to get the Citrix Receiver installed. The first thing we need to do is download the .apk (Android Package) file. Normally, I would just go to http://www.citrix.com/receiver and choose “Android”. But, as of this writing, when you do that, you are redirected to the Android Marketplace. Unfortunately, Android Marketplace does not work on the Android Emulator. So, here is what you can do instead:
Go to http://www.citrix.com/downloads and choose “Receiver for Android” from the drop down list. From there, you can select the Android client and download the .apk.
Install the Citrix Receiver for Android
Ok, so now we have a functioning Android emulator and the Citrix Receiver downloaded. The final step is to install the Citrix Receiver onto the emulator. Here’s how:
Copy the .apk file to %ProgramFiles%\Android\android-sdk\tools
Open a command prompt and change the directory to %ProgramFiles%\Android\android-sdk\tools
With the AVD you created running, execute the following command: