My blog is currently built in Drupal, a choice I made a few years ago because I had absolutely no time to do anything else and I wanted to have a blog up & running in a matter of a few hours with full flexibility and extension capabilities with a perssonal hosting as well, that's the reason why I didn't take any of the blog providers.
That said, I wouldn't say that it was the happiest choice in my life and now I'm too lazy to make a migration (content wise) to something else! As more and more devices visiting the Internet are mobile ones, I have decided to create a mobile version of this blog. If you're using a mobile device, you might already be viewing the mobile version. By the way, if you use an iPhone, don't hesitate to add a shortcut to your home screen to benefit from a full screen view.
I've added a webcast viewer in the mobile view. For now, I have only one webcast but I plan to record some modules soon. I'll start with an ALM module containing a few videos. It's not a new topic nor is it specific to 2013 but I realize in my day to day activities that it's still hard to do good ALM in SharePoint and to handle deployments properly, especially in large shared environments. I'm collaborating a lot with the infrastrcuture teams and understand their concerns when it comes to Farm Management.
That's why I've decided to share my experience around those topics, starting from the very basics to the most complex.
Hopefully you'll enjoy it.
I'll be writing a series of blog posts explaining how to develop mobile applications for SharePoint. Here is what is planned:
In this blog post, I'll be talking about the various possibilities to design mobile apps for SharePoint. You'll also see what's my preferred framework and I'll give some input on what are the key factors to take into account in order to make a choice. Of course, the choice will always be yours, my goal is just to give some tips.
In this blog post, I'll be talking about how to integrate the Sencha framework with SharePoint. I'll build a small app and will give the necessary explanations to understand the interactions between Sencha & SharePoint.
I'll go a little bit further and show how to build a production ready Sencha Package and how to deploy it properly into SharePoint. I'll also go a little bit further regarding the interactions (read/write) operations from a mobile app and custom server-side components that are more suitable for communications purposes.
In this blog post, I'll be talking about how to integrate PhoneGap together with Sencha & SharePoint.
In this blog post, I'll be talking about SharePoint 2013 specific features with regards to mobile development
If you didn't read the first part, I encourage you to do so before going any further. In this second part, I'm going to show you how to develop a very simple mobile app for SharePoint.
As mentioned in my previous post, I've opted for Sencha as a mobile framework. Sencha is a free framework for non-commercial applications and cost about 400€ if you want to distribute commercial applications. For a good overview of their product, you can of course visit their web site at http::/www.sencha.com. It gives the information you need to know to get started, a lot of documentation and a growing community using their forums.
In this blog post, I'm going to show you how to build a basic mobile app that will get some data from a SharePoint list. We will collect items from an Announcement list :
I'll be starting a new series of blog posts about mobile development and SharePoint. On a recent project, I've been in charge of making a POC in order to make a SharePoint 2010 Intranet available on mobile devices. Of course, the goal was to really benefit from the device capabilities.
The main target was iPad. My first reaction when looking at these requirements was that with a tablet such as an iPad and soon Microsoft Surface, your web sites don't need to be so mobile-ready to be browsable & usable.
Indeed, my opinion (that's mine only) is that the added value of a mobile site/app is really there when targeting phone devices because they have such a small screen, a poor keyboard that it's often very boring and tedious to interact with a non-mobile web site.
That said, I kept of course the phones in mind when working on the POC.
In this first blog post, I'm going to talk about the different possibilities we've analyzed (me & the development team) and the choices we made that were IMHO the most relevant. In the next blog posts, I'll enter more in the technical details and some demo code. Note that all what I'll state in this series will be valid for SharePoint 2007, 2010 and even 2013 although the latter has a new plumbing & controls to facilitate cross device implementations.
Native App VS Mobile Framework
As you might know, there are several ways to tackle mobile implementations. If we think of Apple's AppStore, we all know that we can easily install an app from the AppStore such as Twitter, Facebook etc.. and start using it. Usually, this is a very convenient way to leverage all the capabilities of your mobile device and these apps are very user friendly.
What's a native app
A pure native app is specifically packaged for a mobile operating system such as IOS, Android etc.. and deployed either to an Enterprise AppStore, either to a public AppStore.