If we want to develop simple workflow through SharePoint designer in the office 365 for SP 2013 site, then what is the best way to do that?

Should we access office 365 site through SP Designer 2013 installed in a client machine?

Since there is restriction of using SP designer in production then how to develop the same workflow for O365

Hi,

As far as I know the options you have:

• Develop custom Workflow as an APP (requires development)
• SharePoint Designer
• Third party tools (Nintex, K2 etc.)

However as you've mentioned already, SharePoint designer is not recommended in Production environment and in Office 365 there's no traditional dev/test environment. However, I think you can try the following to use SharePoint designer in SharePoint Online:

• Create a test site collection in SharePoint Online
  
• Develop workflow using SharePoint Designer
• Test workflow
• Happy with testing, move the workflow to prod site collection.

Hi,

If you only want to develop simple workflow in SharePoint online, I suggest you create a test site and create workflow using SharePoint designer 2013, you need install it in your client machine to access SharePoint Online.

Like the screenshot below:

Best Regards

• Develop custom Workflow as an APP (requires development)
• SharePoint Designer
• 
  

• Happy with testing, move the workflow to prod site collection.

Hi,

Visual studio is more like developer tools whereas SharePoint Designer is more targeted for Power Users. There's few points you can consider:

1. For simple workflow you can use SharePoint Designer. But if your workflow has integration with other system or has complex logic (for example, get data from SAP for the user, calculate leave etc.) then you better use Visual Studio to develop the workflow.
2. Visual Studio requires developer experience (C#, JavaScript etc.) and if you are a developer you would prefer Visual Studio. But if you are PowerUser, then definitely you can use SharePoint Designer.
3. Power User provides rapid/quick solution in an organization - like using InfoPath, SharePoint Designer, Access etc. However complex solution requires developer involvements. So you can compare your requirements/situation and decide accordingly.

Long story short, Visual Studio is for more developer-like and for complex workflows as per my opinion. I'm a SharePoint developer/architect and never developed SharePoint Designer workflow. Whereas PowerUsers will prefer SharePoint Designer as they will not work code in Visual Studio.

Simple strategy you can follow, can the workflow be developed with SharePoint Designer, if yes then go for it. Otherwise look for alternatives  - Visual Studio, Nintex etc.