top of page
Untitled design (6).png
Product

Get visual review comments, sooner and in context.

Install Livecycle to your existing preview environments to collect visual feedback on your latest code changes.

TL;DR
Less context switching.
Faster feedback loops. 
Better developer experience.

Untitled design (6).png
How it works

3 minutes. 3 commands.

Quickly install the Livecycle SDK to any environment:

Step 1

Open a branch

npm install livecycle-sdk

Step 2

Install the Livecycle SDK

import { Livecycle } from 'livecyclesdk'Livecycle.init ()

Step 3

Initialize the SDK at the root of your project:

Step 4

Open a pull request

livecycle link --from-git . --url="<url>" --api-key="my-api-key"

Step 5

Link your preview environment to a Livecycle playground:

Step 6

Get ridiculously clear, contextual feedback on your latest changes

That's it.
It's that simple.

Untitled design (6).png
How it works

3 minutes. 3 commands.

Quickly install the Livecycle SDK to any environment:

1

Open a branch

2

Install the Livecycle SDK

npm install livecycle-sdk

3

Initialize the SDK at the root of your project:

import { Livecycle } from 'livecycle-sdk'Livecycle.init ()

4

Open a pull request

5

Link your preview environment to a Livecycle playground:

livecycle link --from-git . --url="<url>" --api-key="my-api-key"

6

Get ridiculously clear, contextual feedback on your latest changes

That's it.
It's that simple.

Anti-FAQs

Work the way you want.

Livecycle integrates with the SCM tools, communication apps, and task management platforms you're already using.

images.png
gitlab-logo-png-transparent.png
atlassian_jira_logo_icon_170511.png
5cb480cd5f1b6d3fbadece79.png
logo-padding-1622840635.png
6125001.png
Clickup-Logo-web.png

coming soon...

Screen Shot 2022-10-11 at 19.16.20.png

Trusted by great developers.

Untitled design (6).png
Untitled design (6).png

Frequently asked questions

  • I'm already set up to produce preview environments for my PRs. Is Livecycle relevant for me?
    Absolutely. We've just launched our SDK for exactly this use case. With just a few commands, you can install Livecycle to your existing pipeline and get our visual annotation layer built-in to those preview environments.
  • What preview environment services are supported?
    Livecycle can be installed quickly on virtually any existing preview environment platform or service, including the big names like Netlify and Vercel, and pretty much any of the more boutique alternatives available. All you need to do is install and initialize the SDK, open a PR and link the preview environment to Livecycle one time. Then, all your preview environments will include the Livecycle annotation layer and smart notifications.
  • How much does it cost?
    We’ve got a free tier to get started and we're free forever for Open Source projects. For ongoing, long-term use, we’ll be introducing a per-seat pricing model.
  • What happens to the feedback that is left in Livecycle? Do I need to copy and paste it by hand into my issue tracker??
    Every comment you receive in Livecycle, that you address within the context of the original ticket (i.e. the same branch) doesn't have to make it into the issue tracker, since it's handled "on the spot". If there are comments that exceed the scope of the original work (basically anything that you understand should be a standalone issue), you can send them from Livecycle directly into your issue tracker. We currently support Linear, and plan to support JIRA and ClickUp in a couple of weeks.
  • How will I know when people leave me feedback in Livecycle?
    Our smart notifications let the relevant folks know when something important has happened - if you've been invited to a playground, if you have a new comment or mention and more. You can set up these notifications for email or with a dedicated Slack channel that will keep everyone on the team posted when there's new activity for a PR that's under review.
  • What's the point of having others leave feedback in an unstable environment that isn’t ready to be fully tested?
    The best practice for using Livecycle is sharing an environment once it reaches a PR stage - meaning your PMs, UX and other stakeholders are actually reviewing your code outputs while your peers are reviewing your code.
  • I already have an iterative review process with my team. What value does Livecycle add?
    Iterative communication is at the heart of what we do at Livecycle. Our aim is to make the iterations shorter - by making feedback arrive in the right time and place. Using Livecycle doesn't require you to do things differently, it just lets you do things better and more effectively. Less context switching, clearer feedback in context, and faster PR turnarounds.
bottom of page