The workflow between an agency and a client for creating a digital publication, using Adobe DPS.
This can be somewhat of a tricky and quite complex area to understand. So, we’ll try to keep it as simple as possible by giving more of an introduction and brief overview. But, once you have read and understood our interpretation, further reading can be found here, which goes into far greater detail.
The simplest workflow: The agency does everything.
The agency builds the app, creates the content and then submits the app.
It does have many drawbacks though…
In essence the agency ‘owns’ the app, meaning:
– For as long as the app lives it will always ‘belong’ to the agency, it cannot be moved to another DPS account. Well, DPS does not support this, but technically it can be done, but most of the functions that DPS offers may not work properly.
– When in the app store, the app – in the small print – will display the agency name, not the clients.
– Only the agency will have access to the app analytics, which will then need to be presented to the client.
– A client cannot distribute private apps in this way.
To overcome the above drawbacks, the client must publish the app themselves.
This allows the client to ‘own’ the app. Meaning:
– The client can use another agency, or work on the app themselves in-house – basically they are not tied to one agency.
– The client can create a privately distributed app.
– The clients name appears on the app, in the small print.
There are four ways this can be done, depending on the level of security that the client is happy exposing to the agency, and so a large part is the confidence and trust the client has in their agency. In basic terms the first workflow is the least secure and the fourth the most secure.
Here the agency creates the content (folio) and builds the app, using the clients DPS account details along with their security certificates. The clients can then submit the app themselves. The agency can continue to create new content and publish it to the app.
The client gives access to the agency to create and publish the content (folio) only. The client builds the app themselves, with assistance from the agency when needed. This approach means the client does not have to give the agency their security certificates (which are required to build an app), which helps to reduce security concerns.
This approach also allows the client to work with a number of different agencies, whom can all produce content for the client’s different apps.
The next two workflows are a bit more complex, therefore requiring more effort and liaising between the agency and client. They are for when security is paramount. And, like we have done with the previous workflows, we cover them in brief terms.
In a nutshell the client shares an empty folio with the agency. The agency can then add articles to the folio and work on them during the process.
Because the client has shared the empty folio with the agency, they have separated the content creation and publishing functions. So only the client is responsible for publishing the content, when they are ready.
Even more secure, the client can wait until the folio has been approved, before it enters the system to be published. In essence the agency shares their finished folio with the client, the client then copies the content to their final folio, which is then published.
There are no specific rules from governing bodies, on the DPS process. The agency needs to sit down with the client to make sure they are aware of the available workflows, and decide on a workflow that suits them.
Factors such as the type of information they are publishing / industry they are in, purpose of the app, the in-house app capabilities of the client, and of course the trust the client has in the agency, will all help determine the workflow that is appropriate.
We’re not just saying it, but an agency is the partner of a client, so they will guide the client through the process, assisting them at every stage and so making the workflow as easy as possible and always so everything that is done is in the clients best interests.
If you are considering a digital publication for your organisation, please do get in touch, we’d be happy to help.
Until next time