Posts by nilsmielke

    I agree with almost everything written here before me. Here’s my two cents, though.


    1. More communication = less uncertainty
    I love working with Perch and would love it to evolve and prosper. I don’t care too much, when v4 will land, but to keep selling Perch to my clients, the occational sign of life would be helpful. With every quote I write, I am pondering whether or not to propose Perch and whether or not to quote for an ongoing maintenance fee. It could be considered easy money, if there is only one update a year, but that makes you wonder, where Perch is headed and might lead to unpleasant discussion with clients. (Also, an approximately bi-monthly update cycle, gave us a good “excuse” to be in closer touch with clients.)


    2. Subscriptions are not for everyone
    As for the pricing model: We are a tiny two-man-show of an agency, sometimes outnumbering the headcount of the companies we work for. Some of those wouldn’t care for a monthly subscription. Some already opt for not buying the ongoing maintenance. Our bigger clients wouldn’t object, I suppose, as long as they get value for their money—in the form of more regular updates.

    I think, Hussein’s suggestion would work quite well for us.

    I understand that some customers who run agencies may have a very large number of licenses so paying for updates per license may be a big turn off. Perhaps additional options could be provided:

    • (A) Pay updates per license (suitable for those who have a small number of licenses and/or those that do not need to get updates for all licenses). You don't have to pay if you don't want the updates.
    • (B) Pay a single fixed subscription fee to get standard Perch updates for all the licenses in your account. Use (A) for your Runway licenses.
    • (C) Pay a single fixed subscription fee to get standard Perch and Runway updates for all licenses in your account.

    Depending on the cost of (B) and (C), another option (D) could be to decide per licence, if it should run on a subscription or not. That we could factor in with the ongoing maintenance, some of our clients choose to buy.


    I know, Perch probably cannot serve everyone and every scenario, if it should stay/become sustainable. It did that pretty well for us in the past, though, and I enjoy using it even on the smallest of projects.

    Hi Design,

    here’s how I have done it:

    In your page (e.g. “project.php”), after including Perch‘s runtime.php and before including the header, tell Perch what image to use.

    Then in your header.php set the meta tag for og:image with that image:

    PHP
    1. <meta property="og:image" content="<?php print PerchSystem::get_var('ogimage', true); ?>" />