Appassion
  • Appassion Rules Intro
  • Bubble Rules
    • Bubble Naming Conventions
      • Bubble Design Convention
      • Bubble Workflow Convention
      • Bubble Database Convention
    • Bubble Project Preparation
  • Onboarding Guide
Powered by GitBook
On this page

Onboarding Guide

Welcome to Appassion! We are thrilled to have you on board as part of our dynamic team specializing in creating MVPs and no-code projects. At Appassion, we pride ourselves on fostering a collaborative and innovative work environment where every team member has the tools and support they need to succeed. To ensure that our processes run smoothly and consistently across all projects, we have created this guide to help you get started.

This section is designed to familiarize you with the essential rules and practices for both developers and project managers. Whether you're coding a new feature, managing client expectations, or planning the next steps in a project, these guidelines will provide clarity and structure to your workflow.

Please take the time to review the following information and don’t hesitate to reach out if you have any questions or need further assistance.


General Rules (Applicable to All Roles)

  • Work Schedule: The workday is from 10:00 AM to 7:00 PM. If you need days off or time off, notify Ilana or Alexandra in advance.

  • Availability: Be available on Telegram during work hours (10:00 AM - 7:00 PM on weekdays).

  • Task Management: Maintain tasks and their statuses in the corresponding task trackers, such as Trello. Make sure to have tasks updated based on current state, assign required status or add comments if needed.

  • Time Tracking: Always use Clockify to track your work hours. Ensure to add projects and provide detailed descriptions for the time tracked.

  • Communication:

    • Respond promptly to messages on Telegram to maintain smooth communication.

    • Inform the relevant team members immediately if you encounter any blockers or delays.

  • Vacations and Holidays:

    • Employees are entitled to 28 vacation days per year.

    • All local public holidays are observed as days off.

    • Vacation requests must be approved in advance by Pargev, Ilana, or Ivan.

  • Corporate Emails: All employees should use their corporate emails (@appassion) for testing the apps and other related tools used.


Instructions For Developers
  • Code and Project Standards:

    • Ensure project consistency by using Appassion's internal documentation. This creates first impression of our work when the app is opened by the potential client or other team members.

    • Test your work thoroughly before submitting it for review to one of the Project Managers (Ilana, Alexandra or Pargev).

    • If you encounter issues during the development process, make sure to inform your project manager and communicate to find a solution. The most important is not be afraid to ask for a help - we are all working as a team. Feel free to always reach out to the managers or other devs.

  • Task Management:

    • Keep your tasks updated in the corresponding task tracker (e.g., Trello).

    • Inform the project manager when a task is ready for testing.

  • Timing:

    • Provide time estimations for tasks and ensure that tasks are completed within the specified timelines.

  • Handover Process: If you're stepping away from a task or project, document your progress clearly to ensure a smooth handover to another developer.

    • If are onboarded on a project that another team member previously worked on - make sure to learn all the existing flows before implementing changes. Workflows are there for a reason, it is better to reach out to that team member to ask the related questions.

  • Deployment Best Practices:

    • Always merge branches carefully to avoid overwriting or losing changes. Coordinate with your team to ensure all updates are incorporated seamlessly.

    • Each deployment must be approved by the project manager before proceeding.

    • Double-check the live environment post-deployment to confirm that the changes have been applied correctly and everything is functioning as expected.

  • Continuous Improvement:

    • Follow best practices and coding standards for Bubble development.


Instructions For Project Managers
  • Centralized Information: Keep all project-related information centralized in one environment (e.g., Trello, Telegram chats). Ensure developers have access to the Bubble project, task tracking tools, and all related environments.

  • Project Setup:

    • Create a new project in Clockify and set up a dedicated chat in Telegram.

    • Organize and assign tasks clearly in Trello or the designated task tracker.

  • Task Management:

    • Maintain an updated task list with clear deadlines and priorities.

    • Regularly review task statuses to ensure progress aligns with the project timeline.

    • Follow up developers to check current status of a tasks, identify issues (if any). If required have another team members involved to tackle the issue accordingly.

    • Make sure you have an understanding on how much time each task it expected to take. With that, always check the devs are not spending too much time on a particular task.

    • When describing tasks in Trello, ensure the task title is clear and concise. Use the description field to provide detailed steps, relevant links, and any necessary context. Always include attachments or screenshots if applicable to avoid confusion for developers. Add loom videos as well to make the task even more clear for the devs.

    • Make sure to check with particular devs what language they would like to have tasks described in - English/Russian. With all clients we communicate in English, therefore the tasks are initially in English, however to ensure the devs are understanding the tasks fully translation might be required.

  • Roadmap and Planning:

    • Have a clear understanding of upcoming tasks and the general roadmap.

    • If details are missing, coordinate with Pargev to gather information and create a detailed plan.

  • Communication and Support:

    • Ensure consistent communication with the team and address any issues promptly.

    • Support developers by providing them with the necessary resources and guidance to complete their tasks effectively.

  • Client Interaction: Act as the primary point of contact for clients, providing updates and managing expectations.

    • Make sure to reply to customers in a timely manner—ideally within one hour during the working day.

    • Ensure all messages and emails are free from grammar errors.

    • Reach out to support teams of services we work with to provide clarity for both clients and developers regarding next steps.

    • Keep clients updated on project progress by sharing weekly updates in Slack. Ideally, maintain a dedicated task tracker with the client, separate from the internal task tracker.

    • If any actions are required from the client (e.g., sharing access, undergoing verifications), communicate these requirements in advance and provide detailed, step-by-step instructions.

    Testing and Quality Assurance:

    • Ensure that the feature or app is working properly before delivering it to the client.

    • Conduct thorough testing to identify and resolve any issues.

    • Instruct clients on how to test the feature or app, providing them with the necessary links and credentials as needed.

    • If a feature of functionality is complex or complicated, record a loom video for the client to instruct them on testing. Loom videos can also serve as addition to weekly updates.

  • Handling Feature Requests Outside Initial Scope:

    • If the client requests features outside the initial scope, inform them that the feature can be estimated, and if approved, it can be worked on in the next development milestones.

  • Deployment Approval:

    • Ensure that each deployment is approved by the client before proceeding.

  • Finalizing the Project:


By following these guidelines, we aim to create a productive and collaborative work environment for everyone at Appassion. If you have any questions or require clarification, feel free to reach out to Ilana, Alexandra, or Pargev.

PreviousBubble Project Preparation

Last updated 3 months ago

Share knowledge or helpful resources with the team during meetings or on communication channels. We use the following for storing such updates.

Use this as an example of road map planning. Create copies of this file for your clients.

When the project is finalized, send the client the following message: . Ask them to provide a review and touch base regarding the next steps and project maintenance.

telegram channel
template
Finalization Message