The Facebook project requires separation of the application function from the platform. Check what to determine before measuring integration or campaign tool.
Explain what the app should do
The password “Facebook application” may mean different ideas: a campaign tool, a form on your own website or integration with corporate processes. Before talking about the performance, describe the user's task and the place where it is to be performed. Not every function requires action inside the social platform.
For a company from Krakow or another locality, is also important way of serving the recipients. Is the application supposed to direct to a local event, collect inquiries or share materials? The purpose affects the scope of content and further path more than the name of the service from which the user comes.
Confirm dependencies before designing screens
If the solution uses an external platform, the contractor should first verify the availability of the required functions, conditions of use and the required permissions. No valuation should be based on the assumption that the former mechanism still works or is available to each account.
Write down requirements in the form of questions: what data is needed, where are they coming from, and whether the goal can be achieved with a smaller scope of integration? Also, set account responsibility and handle changes on the supplier side. Such dependence is part of the maintenance of the product.
Example: a campaign to direct to its own tool
Suppose that the brand wants to allow the recipient to choose a variant of the service. Instead of immediately building an extended integration, you can check the prototype configurator on your own website to which the campaign leads. The company then controls the content of the tool and can assess whether the questions are understandable.
Only after checking the basic path it is worth considering additional connections. If the application collects information from users, the scope of the data and the method of further handling must be described in the project. Do not add fields solely because it can be technically obtained.
What should be in the briefing?
- One user task and the expected result.
- Application and traffic sources.
- Needed data, permissions and external relationships.
- Screenplay in case integration is not available.
- Owner of accounts, content and later maintenance.
It is worth starting with a small function test, which will answer the question of feasibility and the sense of solution. More about this approach can be found in the text individual web applicationsCampaign communication discusses interactive advertising design.
