Major pitfalls of custom app development for Dynamics CRM

So, you’re thinking about developing your own Dynamics CRM application? Let me stop you right there! Starting from scratch brings many difficulties for which you might or might not find an effective solution to.

I don’t want to be the bad guy here, but I’ll just say it flat out: Developing your own CRM app is not the best idea.

Okay, it might seem a tad bit biased coming from someone working for a company that developed their own CRM app.  But – from fellow app makers to aspiring app makers – let me shed some light on the pitfalls that might sooner or later sneak up on you:
 

1. Creating an app takes time. Loads of time.

More than you think. More than you predict. We know. We have been developing our Mobile CRM for 5 years now and there are still things to be added or improved. By the time you get started with your analysis, development and tweaking; others’ ships will already cruise the sea.
 

2. Android, iOS or Windows?

Mobility is happening on many platforms – there are Androids with generally wider range of possibilities; there are iOS devices, which are more popular among people. Then, there is also Windows 8 with their Office and enterprise support… It is difficult to pick one and even more difficult to master them all. You might be getting yourself into a pickle here.
 

3. Let’s talk offline

Offline mode is a very difficult problem that requires a carefully planned and executed synchronization mechanism, which takes into account all corner cases. It’s almost impossible to accomplish. We have invested many, many man-hours in it – and believe me – it wasn’t easy.

To get a little insight, read Resco’s technical deep dive into the synchronization process.
 

4. Functionality

There is a big list of features which are useful in mobile CRM scenarios. With custom development, you are much more likely to restrict yourself to just a few (whether it’s because of time, money or technical constrains). You might not be interested in all the features Resco offers at this point, but in the future when your needs change; there is a big chance we have them covered.
 

5. Your app is ready. Or is it?

Let’s say you have decided to go down the development path anyway and created an app. Now you need to submit it to the app store (or install it manually). But what happens when you want to change something? Even the slightest alternation will require you to recompile and re-deploy updated version of the app on the mobile device. Again & again.
 

Afterthought

As you can see, developing your own app is no walk in a park. You’ll face with many challenges (these aren’t certainly all of them). Wouldn’t it be better to focus on the business instead of struggling with different platforms, technical details, tricky deployment and time?

Maybe go with something that’s tested, proven & ready to use. Like Resco Mobile CRM perhaps?

One thought on “Major pitfalls of custom app development for Dynamics CRM

  1. Before reading your post I thought that developing apps is a very simple process but I am wonder to know the difficulties which we have to face for develop any app. Most important and unique facts have come across to my through this post and A thing which I have liked most that I have known the pitfalls of custom app development by reading this post. before this I only knew the benefits of custom app development. thanks for raising my knowledge.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s