<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by MONK Software on Medium]]></title>
        <description><![CDATA[Stories by MONK Software on Medium]]></description>
        <link>https://medium.com/@monksoftware?source=rss-28dd4b33af4f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HM1IqOGNRk97PivA.jpg</url>
            <title>Stories by MONK Software on Medium</title>
            <link>https://medium.com/@monksoftware?source=rss-28dd4b33af4f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:07:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@monksoftware/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Conversations and brand relationships in the age of Covid-19]]></title>
            <link>https://medium.com/@monksoftware/conversations-and-brand-relationships-in-the-age-of-covid-19-96d0c60cbf71?source=rss-28dd4b33af4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/96d0c60cbf71</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[marketing-technology]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[conversational-ai]]></category>
            <dc:creator><![CDATA[MONK Software]]></dc:creator>
            <pubDate>Thu, 16 Jul 2020 09:05:41 GMT</pubDate>
            <atom:updated>2020-07-16T09:06:40.936Z</atom:updated>
            <content:encoded><![CDATA[<h3>Conversations and brand relationships in the age of Covid</h3><p>Each year, I anxiously wait for the <a href="https://wearesocial.com/it/blog/2020/01/report-digital-2020-i-dati-global">WeAreSocial annual report</a> as if it was a lighthouse for my working strategy from January to December. This year — the year of (dis)grace 2020 — this was the outlook:</p><p>And this was what they said about the internet usage in 2020:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BU4e44LPWXVZJgyME-L5AQ.png" /><figcaption>WeAreSocial Global Report 2020</figcaption></figure><blockquote>The average internat usage this year will spend an time online equal to 100 days (6 hours and 43 minutes per day): that means in 2020 we will collectively spend 1,25 billion years online. More than 1/3 of this time, 2 hours and 24 minutes per day, is spent on social.</blockquote><p>The leaderboard, when speaking of social media, didn’t differ much from the one of 2019, with Facebook, Youtube and WhatsApp firmly at the top of the list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6cpbYJX4HML_VGrl04lJ7Q.png" /><figcaption>WeAreSocial Global Report 2020</figcaption></figure><p>That was before the lockdowns, before the pandemic, before everything was about to happen.</p><p>When the Covid-19 spread, the sole Facebook (including Messenger and WhatsApp) <strong>grew 70% in usage in Italy since the start of the crisis</strong>, with group calls going up to 1.000% in one month (on top, <a href="https://www.corrierecomunicazioni.it/digital-economy/ecommerce/e-commerce-ricavi-a-20-in-crescita-la-spesa-media-per-utente/">e-commerce saw +40% buyers in April</a>).</p><p>In a word, digital has turned into “the new normal” becoming the relationship channel <em>par excellence</em>.</p><h3>A digital leap forward that caught many unprepared</h3><p>This unexpected shift brought us to <strong>a point we would have normally reached maybe in 5–10 years</strong>. Businesses of any size and type now have to <strong>rethink and digitalize</strong> their external processes as well as the internal ones.</p><p>The overall framework is one where the <strong>internet audience is going to be way bigger than expected</strong> in a little time, with relationships turning into <strong>e-relationships </strong>and raising to the <strong>status of “primary goods”</strong>. At the same time, there’s a<strong> huge gap among users in terms of digital literacy</strong>.</p><h3><strong>5 must-do for companies to manage the shift</strong></h3><p>Communication clearly becomes king (and queen, if not the whole court!) for companies.</p><p>But most important is to do it right.</p><h3>1. Create a customer centric user experience</h3><p>“Customer centric” is the real deal in 2020 and UX becomes essential, as we cannot ignore anymore the need for a low learning curve, especially in the very first virtual approaches with a brand. A company storytelling goes also through technological choices and, in such a situation, keeping it simple and accessible can also be regarded as an ethical choice.</p><h3>2. Use contact management as a positive battlefield</h3><p>Empathy, presence and immediacy are going to be the values upon which any communication will be based. At the same time, the focus must be on expectation management and cost management, especially considering that “peak” situations will likely be more frequent than before.</p><p>Curious to discover the other points? Visit the full blogpost here: <a href="https://tinyurl.com/digital-after-covid"><strong>https://tinyurl.com/digital-after-covid</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96d0c60cbf71" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hackathon: 7 miti comuni da sfatare o confermare]]></title>
            <link>https://medium.com/@monksoftware/https-medium-com-hackathon-7-miti-da-sfatare-o-confermare-5bea832ef445?source=rss-28dd4b33af4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bea832ef445</guid>
            <category><![CDATA[eventi-roma]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[hackaton]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[MONK Software]]></dc:creator>
            <pubDate>Thu, 07 Mar 2019 08:01:00 GMT</pubDate>
            <atom:updated>2019-03-08T22:25:18.153Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hackathon sì o hackathon no? E’ il dilemma che molti sviluppatori in cerca di nuovi stimoli si pongono spesso davanti a eventi di questo tipo. In attesa di MMH 2019, abbiamo esaminato i pregiudizi più comuni e vi diciamo quali, secondo noi, sono veri e quali no.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d0WMGVVwj166oM3jvV0DNg.jpeg" /></figure><p>Degli hackathon si dice tutto il contrario di tutto: che siano ottime occasioni per trovare lavoro, che non lo siano, che aprano grandi opportunità per chi porta avanti un progetto valido e che non lo siano poi tanto.</p><p>Comunque lo si veda, insomma, a parlare di hackathon si rischia di inciampare in pregiudizi e cliché. Ma quali di questi sono veri e quali sono, per lo meno, discutibili? Ce lo siamo chiesti spesso e, ora che stiamo organizzando il primo <a href="https://www.eventbrite.it/e/biglietti-mmh-monk-mobile-hackathon-roma-56814185759">MONK Mobile Hackathon</a>, abbiamo raccolto abbastanza esperienze da scardinare o confermare i miti più comuni. Quali sono? Ecco una lista che vogliamo condividere con voi:</p><p><strong>Mito n. 1: devi essere un esperto assoluto della materia trattata per partecipare – falso</strong></p><p>La parola d’ordine durante un hackathon è “sperimentazione”. Siamo nel contesto della open innovation per eccellenza, dove sapere tutto su un argomento può essere tanto un punto di forza quanto un punto debole, se si imbriglia il progetto dentro regole troppo rigide.</p><p>Certo, alcune competenze di base sono necessarie (vi presentereste mai a un contest di cucina senza sapere come si accende un forno?) ma la vera forza di un hackathon è quella di essere un po’ l’equivalente operativo di un brainstorming: si incoraggiano i progetti selvaggi, si testano nuove tecnologie, si fa tutto quello che in situazioni più strutturate si farebbe mai.</p><p><strong>Mito n. 2: un hackathon è una delle migliori occasioni di networking per uno sviluppatore (e non solo) – vero</strong></p><p>Diciamolo: un altro enorme punto di forza degli hackathon è la capacità di unire personalità e professionalità diverse sotto lo stesso tetto e vedere cosa può venirne fuori. La parte più interessante è proprio quella dell’interazione con gli altri: si condivide un obiettivo, si costruisce in poche ore un’empatia che a volte sorpassa quella di mesi trascorsi accanto ai colleghi in situazioni ordinarie. E, soprattutto potete scambiare competenze e bigliettini da visita con la stessa facilità con cui andreste da GameStop a comprare il videogioco dei vostri sogni.</p><p><strong>Mito n. 3: Gli hackathon sono anche divertenti – vero</strong></p><p>Che agli hackathon ci si diverta è vero. Anzi, verissimo. Se avete già partecipato a uno, lo sapete – oppure potete chiedere ai vostri amici: tranne in casi più unici che rari, tutti vi confermeranno che stare nell’hackathon è la parte migliore dell’hackathon stesso. Il progetto di base conta, la vostra capacità di dare il meglio anche, ma sono l’energia del gruppo e l’entusiasmo che si respira in un contesto simile a renderlo speciale. Non è una maratona che dovete correre da soli: il gioco di squadra vi permetterà di restare sempre leggeri anche dopo ore e ore di duro lavoro.</p><p><strong>Mito n. 4: Le aziende organizzano gli hackathon per trovare idee a basso costo – falso</strong></p><p>Forse qualche anno fa, quando il fenomeno hackathon è esploso, alcune aziende potrebbero averci visto una miniera ininterrotta di idee da cui attingere a piene mani nei momenti di “blocco creativo”. A torto o a ragione, però, i fatti hanno smentito questo mito.</p><p>E’ vero che un hackathon mette sul piatto molti nuovi spunti, ma il ritorno per l’azienda non viene quasi mai dalle idee di per se stesse (e, per spiegare perché, torneremo su questo punto nel prossimo mito da sfatare) quanto dalla comunicazione, dalla cultura dell’innovazione che l’hackathon promuove e dalla contaminazione di idee e approcci di vario tipo.</p><p><strong>Mito n. 5: la proprietà intellettuale delle idee va agli organizzatori – falso il più delle volte</strong></p><p>Una paura comunissima tra chi partecipa a contest in cui a farla da padrone sono le idee è proprio la perdita della proprietà intellettuale su un progetto. Può darsi che abbiate nel cassetto l’idea del secolo ma non abbiate i mezzi per realizzarla. Ecco che leggete il bando di partecipazione all’hackathon dell’azienda XYZ e vi si apre l’opportunità di farvi conoscere e persino di trovare finanziatori per la vostra startup. Qui, i dubbi iniziano a tormentarvi: cosa succede se vi rubano l’idea? E se la prendono e la migliorano e voi restate a bocca asciutta?</p><p>Potete stare tranquilli: capita che alcuni hackathon prevedano la cessione dell’attività intellettuale all’organizzatore, ma non è la regola e, soprattutto, una condizione di questo tipo deve essere esplicitata in un bando (se ve lo state chiedendo, MMH non prevede in alcun modo l’appropriazione delle idee dei partecipanti. Per saperne di più e registrarvi, <a href="https://www.eventbrite.it/e/biglietti-mmh-monk-mobile-hackathon-roma-56814185759">date un’occhiata all’evento su Eventbrite</a>).</p><p><strong>Mito n. 6: dagli hackathon possono nascere opportunità lavorative – vero</strong></p><p>Vi ricordate qualche punto più su, quando abbiamo parlato di quanto sia facile fare networking? Questo vale sia per chi partecipa a un hackathon sia per chi lo organizza. L’obiettivo di questi eventi è creare valore per le persone e con le persone. Quando cercate lavoro semplicemente inviando un portfolio o un classico CV, state affidando a qualche parola o a una serie di progetti vetrina l’arduo compito di sostenere che siete i migliori. Quando partecipate a un contest del genere, invece, siete voi stessi a dimostrarlo con i fatti.</p><p>Non significa che ogni hackathon sia fatto per assumere persone, ma perché escludere a priori questa possibilità?</p><p><strong>Mito n. 7: siccome organizzare un hackathon è costoso, gli organizzatori vi offriranno un vitto contato e l’ambiente sarà poco confortevole – falso (almeno in MONK Software)</strong></p><p>OK, su questo mito abbiamo barato un poco. Ogni azienda ha il suo e non possiamo parlare per gli altri. Per quanto ci riguarda, ci teniamo a mettere i nostri ospiti a proprio agio e proprio per questo <a href="https://www.google.com/maps/dir/webmonks/data=!4m6!4m5!1m1!4e2!1m2!1m1!1s0x1325898dfcd6fa8b:0x7c46f40c51d6e63a?ved=2ahUKEwiL4sOGxOvgAhWP2KQKHdxnAzEQ9RcwC3oECAUQDg">stiamo organizzando il Monk Mobile Hackathon nella nostra sede</a>. Non che si vada agli hackathon per mangiare o per giocare a biliardino, ma non di solo codice potrà vivere l’uomo, giusto?</p><p><em>Vuoi saperne di più su di noi? Visita il sito </em><a href="https://www.monksoftware.it/"><em>www.monksoftware.it</em></a><em> oppure </em><a href="https://www.eventbrite.it/e/biglietti-mmh-monk-mobile-hackathon-roma-56814185759"><em>clicca qui per registrarti a MMH 2019</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bea832ef445" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Push notifications turned into Rich]]></title>
            <link>https://medium.com/@monksoftware/push-notifications-turned-into-rich-9ebd573bdff5?source=rss-28dd4b33af4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ebd573bdff5</guid>
            <category><![CDATA[marketing-automation]]></category>
            <category><![CDATA[push-notification]]></category>
            <category><![CDATA[mobile-marketing]]></category>
            <category><![CDATA[marketing-tools]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[MONK Software]]></dc:creator>
            <pubDate>Tue, 17 Apr 2018 09:14:54 GMT</pubDate>
            <atom:updated>2018-04-17T09:14:54.571Z</atom:updated>
            <content:encoded><![CDATA[<p>We are living the “mobile first” era and mobile marketing is gaining more power day after day. In the time you have quickly read these words, millions of messages have been sent, push notifications received and online orders purchased. Customers gradually became more aware and demanding, but that’s an amazing news. It means that creativity, personalization and outstanding contents returned as essential in every marketing strategy.</p><p>The other incredible news is that we have all the necessary tools to put them in practice. That’s why everyone should better understand how powerful rich push notifications are.</p><p>Please note this is not a standard article and the adopted point of view is the one of an average client. Which means, in the next paragraphs you are going to learn more about your best friend.</p><h3>Nice to meet you, I am your Very Important Client</h3><p>I read people <a href="http://www.statista.com/statistics/781692/worldwide-daily-time-spent-on-smartphone">spend on average between 3 and 5 hours per day on their mobile</a>, which, I counted, means 155 hours per month and 1860 hours per year.</p><p>Wait, are you saying I spend more than half of the time I carefully invest in pure and restoring sleeping, in scrolling my mobile every day?</p><p>Yes, I do. But how? And when? And…</p><p>Oh. Seriously?? Woooow! Excuse me, I just received a notification that my favorite band is playing in town next month and I do want to book the tickets<strong>.</strong></p><p><strong>Now.</strong></p><p><strong>I mean, Right. Now.</strong></p><p>Yes, mobile marketers, I am the client you should definitely catch! Let’s see why.</p><p>I own a smartphone, like another <a href="https://wearesocial.com/it/blog/2018/01/global-digital-report-2018">5,134 billions of smartphone users</a> around the world. And I do have a conflict relationship with technology, like the <a href="https://www2.deloitte.com/content/dam/Deloitte/us/Documents/technology-media-telecommunications/us-tmt-2017-global-mobile-consumer-survey-executive-summary.pdf">47% of American smartphones owners who recently stated they’re trying to reduce the use of their phone</a>. Nevertheless, I can’t remind the last time I forgot my mobile at home in the past 6 years.</p><p>On top of that, I recently counted 12 apps installed in my mobile, only 5 I frequently use. I am wondering if I should uninstall some of them to free some space… But wait, are you saying I can get an alert when flight tickets for San Francisco are on sale?!? I was just thinking to go next summer! Sure, keep me posted.</p><p>And voilà. You opted me in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/0*mIoSSFwtVLMjmj8o.png" /></figure><p>(source: Cluster as cited in Medium)</p><h3>Understand my tastes: what I like of push notifications</h3><p>The first time I received a push notification I was surprised. It wasn’t a standard alert from any social media I was used to see. Not that time.</p><p>That time was a breaking news about another earthquake in Italy. Did I mention I got obsessed with earthquakes some time ago? Yes, my most visited website has been <em>earthquakes.com</em> for a while and that’s why I felt kind of special when I read the news. I guess it’s the same excitement journalists experience when they find a scoop.</p><p>A couple of days later, I got another alert regarding a new Picasso exhibition in my city. Picasso is my favourite painter.</p><p>An then another, and another, and another.</p><p>After a while I started understanding. The news application I had installed was selecting for me the most relevant news based on my interests and was sending me notifications. I loved it. It was like having a personal consultant perfectly knowing all my tastes. I was wound up.</p><p>Wanna know why?</p><p>Well, I realized push notifications play on me a mix of excitement for “being the first” and sense of imminence to maintain this primacy. If you add to this a very catchy video, trust me, I am totally yours. Which explains very well why I recently bought a 30% discounted iron after Amazon notified me even if I’ve never ironed before. And this explains even more the power of rich push notifications.</p><p>But the fact remains that I do have too many unused apps installed, so, listen carefully: if you don’t want me to uninstall yours, aim for this sense of uniqueness I like so much and court me.</p><h3>Rely on numbers: what statistics reveal about Push Notifications</h3><p><a href="http://www.biznessapps.com/blog/writing-push-notifications">Researches say 50% of smartphones users appreciate notifications</a>, especially if they are personalized. But notifications can be also tricky, you know that. Few are awesome, a bit more than few are borderline, many are a dead-end road.</p><p>For instance, 37% of users disable push notifications if too many are sent. Too many is generally between 2 and 5 notifications received <strong>per week.</strong></p><p>Like in love, less can be really more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/0*wwvsnWu9XW5vjDJO.png" /></figure><p>(source: <a href="http://info.localytics.com/blog/push-notification-survey-2018">Localytics</a>)</p><p>Good news for you, users also wait before stop using the app till 6–10 notifications are sent weekly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*rermjtVlgNcrqf9N.png" /></figure><p>(source: <a href="http://info.localytics.com/blog/push-notification-survey-2018">Localytics</a>)</p><p>Being part of the analyzed sample I can say that, yes, you have another chance to keep me with you. How? Treat me well.</p><h3>App opt-out: fight it with Rich Push Notifications</h3><p>Studies say the average <a href="https://www.accengage.com/it/infografica-tasso-di-opt-in-e-di-reazione-alle-notifiche-push-per-app-mobile-siti-web-e-facebook-messenger/">opt-in rate is about 72%</a>, 100% for Android, 43% for IoS. Are you wondering what to do with the other 28%? That’s so simple. Think of every single user as you thought of me.</p><p>Again. And again, and again.</p><p>For instance, personalization encourage the app usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/0*a3chFLzGCqBSmggC.png" /></figure><p>(source: <a href="http://info.localytics.com/blog/push-notification-survey-2018">Localytics</a>)</p><p>That’s why rich push notifications should be primary in every mobile marketing strategy. In fact, rich push notifications allow you to send custom alerts with videos, images and Gifs, enhancing the engagement of your clients up to an extra 88%.</p><h3>Why PushCamp can be the right solution for your push campaigns</h3><p><a href="https://www.monksoftware.it/solutions/#pushcamp">PushCamp</a> is a modular and scalable service to create Standard and Rich Push Notification campaigns, developed by Monk Software to support marketers all over the world reaching their goals.</p><p>Thanks to PushCamp, you can create the content of your campaign for both Android and iOS in minutes, and segment your target audience by importing your contact list or by creating it from scratch through custom parameters — so to offer your clients the level of personalization they expect and appreciate.</p><p>Once your message and target are up, you can schedule the campaign according to a time scheduling or automate it if specific events occur. Detailed reports will help you analyzing your performance and get better results; everything from a single interface.</p><p>That notification you just received from your mobile provider? Yes, we sent it.</p><p><a href="https://www.monksoftware.it/contact/">Contact Monk Software to find out more about PushCamp</a>!</p><p>PS: And now I’ll tell you a secret. I am a marketer as well.</p><p><em>This article was originally published on </em><a href="https://www.monksoftware.it/blog/rich_push_notifications_marketing/"><em>Monk Software’s blog</em></a><em> by Elena Aceto.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ebd573bdff5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 ways in which Instant Messaging beats Live Chats]]></title>
            <link>https://medium.com/@monksoftware/5-ways-in-which-instant-messaging-beats-live-chats-d5cc21615772?source=rss-28dd4b33af4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5cc21615772</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[instant-messaging]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[live-chat]]></category>
            <category><![CDATA[messaging]]></category>
            <dc:creator><![CDATA[MONK Software]]></dc:creator>
            <pubDate>Wed, 20 Dec 2017 15:12:12 GMT</pubDate>
            <atom:updated>2017-12-20T15:12:12.959Z</atom:updated>
            <content:encoded><![CDATA[<p>Live chats used to be great. When they first came out, they were absolute craziness — they were the future.</p><p>And they still are a very useful tool. But — let’s face it — they’ve lost most of the magic they were surrounded by. Especially since the mobile revolution.</p><p>Countless companies introduced live chats in their business processes, being 100% sure live chats would save their customer service departments’ money and time. All of that, while ensuring an amazing, satisfying customer experience.</p><p>Reality proved to be quite different in most cases.</p><p>Live chats can be good to manage the sense of urgency for some requests, or when there are no “peaks”. But if you’ve ever found yourself in the position of contacting a company’s customer service for help or information, you know how frustrating that experience can be for a customer.</p><p>You might not have to pick up the phone and wait for the company to reply while listening to “Vivaldi’s Spring” in loop, but sitting behind your deck and waiting for an operator to reply can still be stressful. Especially if you are in a hurry. Or if your internet connection is not stable enough to make you feel safe from losing your turn. Or if you are one of those impatient people like me who just need to do something else in the meantime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*SRtmH6nZ-72u47Wd.jpg" /></figure><p>Customers are not the only deceived party in that frame. We have daily conversations with customer care managers complaining about the fact that introducing a live chat didn’t quite ensure the performance they expected.</p><p>Live chat’s broken promises are what made us fell in love with Instant Messaging at first sight. We’ve been working on that for a few years, now, and we have had many chances to compare the two on a daily basis, measuring results. When our clients are looking for a solution to improve their processes and their customers’ engagement, in most cases we would advise them to go for Instant Messaging.</p><p>There are a number of reasons why, but if I had to draw up a ranking of the top 5 it would be these.</p><h4>1. Instant messaging reaches the customer in his/her comfort zone.</h4><p>This statement has many applications. First and foremost, Instant Messaging is by far the most popular UX right now on the digital and mobile landscape, with almost 2 billion users worldwide. That’s because anybody easily learns how to use it, with no distinction of age, culture or else. It comes natural, as it uses a natural interaction and natural language. Doesn’t your mom send you WhatsApp messages on a daily basis, after all?</p><p>Chatting with customers in such a context means to be in the position of easily building a sense of intimacy, reaching them wherever they are — straight on their mobile phones.</p><p>That leads us to reason number two.</p><h4>2. It is bi-directional (for real)</h4><p>With live chats, you have most likely to wait for the customer to contact your company. That significantly restricts its scope and potential.</p><p>With Instant Messaging, instead, you can open broadcast communications or one-to-one communications, with the input coming from your brand itself. Whether it is a marketing initiative for all your customers or a specific CRM offer, you can really reach the right people at the right time, in the way that is most familiar to them. And without being perceived as too intrusive or interruptive.</p><h4>3. It’s asynchronous</h4><p>On a live chat you must reply in less than 30 seconds if you don’t want to indulge in a frustrating experience for your customer (that’s the so-called rule of thumbs). It’s a here and now interaction. When writing to a brand via live chat, one expects the reply to be instantaneous — “live”. But in case of peaks or in case of a small agents’ team, “live” is one of those goals difficult to reach.</p><p>With Instant Messengers, instead, people would normally expect a deferred reply. Just the way it happens for WhatsApp, they would drop a line, put their phone back in their pocket, and keep doing what they were doing before. They won’t lose their turn in the cue if the internet connection drops, nor there will be expired sessions on their way. And they know they will be notified as soon as they get a reply.</p><h4>4. Has conversation log</h4><p>This point is very strongly related to the previous one. Even with an army of operators ready to reply in a few seconds, managing a customer via live chat takes approximately the same time than it does by phone — as a matter of fact, it might take even longer, if you ask me. At least basing on my latest chat with one of the most famous banks of England: one and a half hour behind my keyboard to retrieve part of my credentials.</p><p>Anyways, that means contacting customer care twice costs both in terms of time and money. Instant Messaging allows a massive reduction of recall rate, simply by having the conversation log saved in the customers’ smartphone. If they wrote and asked for their flight number or for their PUK in the past, even months before, they just have to scroll the conversation back to find that information.</p><p>That translates into a higher customer satisfaction and, of course, into an increased efficiency of the overall service.</p><h4>5. It’s not a “tunnel vision”</h4><p>Hands up who did never experience a situation where they are live chatting with a company and the agent would ask you to switch to the email or to the call center to go through your request. That’s the result of most of the things we discussed before: need to go on with the cue, need for more time to retrieve a certain information information, and so on. Which also implies that the customer should start telling his/her issue over and over again, to different people, since the start.</p><p>Instant Messaging, on the contrary, allows longer pauses between a reply and another — if needed. And more likely the user and the agent can start just where they left off. Even switching seamlessly from one agent to another.</p><h3>Which Instant Messenger would be good for your company?</h3><p>While popular IM are certainly to be tapped, we always suggest brands to have their own instant messenger. That is not to compete with WhatsApp or Facebook Messenger, but to fully exploit Instant Messaging’s potential in a branded premise, where your customer’s data are just yours, and where you are able to interact with them the way you need to. That’s why we developed <a href="https://eime.monksoftware.it/"><strong>EIMe (Enriched Instant Messaging)</strong></a>, our solution for companies who want to embrace the conversational paradigm.</p><p><em>This post was originally published on </em><a href="https://www.monksoftware.it/blog/5-ways-in-which-instant-messaging-beats-live-chats/"><em>MONK Software’s blog, by Sara Squintu</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5cc21615772" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coffee speech — VueJS explained in ten minutes]]></title>
            <link>https://medium.com/@monksoftware/coffee-speech-vuejs-explained-in-ten-minutes-6f924fb1c581?source=rss-28dd4b33af4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f924fb1c581</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[vue]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[MONK Software]]></dc:creator>
            <pubDate>Fri, 22 Sep 2017 13:11:03 GMT</pubDate>
            <atom:updated>2017-09-25T13:30:49.289Z</atom:updated>
            <content:encoded><![CDATA[<p>Talking about front-end development, nowadays there are lots of great frameworks (<strong>Angular</strong>, <strong>React</strong>, <strong>Ember</strong>, <strong>Polymer</strong>, <strong>Knockout</strong>, <strong>etc.</strong>) to help developers building powerful, scalable and performing pages. <strong>VueJS</strong> is one of them, but some of its features make it really, really good — and, to some extent, better than the others.</p><p>Don’t get me wrong. <strong>I don’t want to convince you that “VueJS is the way”</strong>, but there are some issues that it solves better than other frameworks.</p><p>Let’s start from the beginning.</p><p><strong>Vue</strong> is a <strong>powerful progressive framework</strong>, very helpful<strong> </strong>to build user interfaces. It is designed to be incrementally adoptable. Its core library focuses on the view layer only, so it’s easy to use and integrate with other libraries or existing projects.</p><p>On top of that, Vue is also perfectly usable for building sophisticated Single-Page Applications when is used with modern tooling and supporting libraries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/0*DR9KugcZLMjesPx9.png" /><figcaption>Angular, React and Vue.js</figcaption></figure><p>Let’s see some of the features that make Vue different from two of the most used frameworks.</p><h3>Angular vs VueJS</h3><p>There are some reasons why you should use Vue instead of Angular. Obviously, they may not be valid for everyone.</p><p>Vue is a more flexible solution that allows you to structure your app as you want, instead of being forced to do everything in “Angular mode”. It’s just an interface level so you can use it as an additional feature of your pages, rather than as a Single Page Application. It leaves you more room to integrate with other libraries, leaving you responsible for architectural decisions.</p><p>For example, <em>the core of VueJS does not contain basic routing or ajax functionality, and generally assumes that you are building the application using an external bundler module</em>. This is probably the most important distinction.</p><p>Angular uses the <strong>two-way binding</strong>. Vue also supports double-sided relationships, but predefined operation is a<strong> one-way, parent-child data flow</strong> between the components. Using the one-way link allows you to study more streamlined data in large applications.</p><p>VueJS performs better and is <strong>much easier to optimize</strong> because it does not use dirty checking. Angular slows down a lot when there are many watchers, because everytime something changes in the domains, all those observers need to be re-checked.</p><p>In addition to that, the digest cycle is performed several times to “stabilize” if some observer triggers other updates — so, in some cases, there just is no way to optimize a scope with large numbers of observers.</p><p>Vue does not suffer from this problem at all, because it uses an <strong>asynchronous queue tracking system</strong> — all changes are triggered independently unless they have explicit dependency relationships.</p><h3>React vs VueJS</h3><p>First of all, <em>internal deployment</em> is fundamentally different. React’s rendering uses <strong>Virtual DOM</strong> — a memory representation how the real DOM should appear. When a state changes, React makes a complete recalculation of the Virtual DOM, compares the differences and then builds the real DOM.</p><p>The virtual DOM approach provides a functional way of describing your view at any point in time, which is really nice. Due to the fact that it does not use observables and recalculates the entire app for each update, the view is by definition assured to be <strong>synced with the data</strong>.</p><p>From 2.0 version, VueJS changed the DOM management passing from using Real DOM to <em>adopting the Virtual DOM</em> like ReactJS do. While in ReactJS when a component’s state changes, it triggers the re-render of the entire component sub-tree, in VueJS component’s dependencies are automatically tracked during its rendering, so the system knows precisely which components actually need to re-render when state changes.</p><p>In the API environment, a problem with React (or <strong>JSX</strong>) is that the computing function often involves a lot of CPU logic, and ends up to look more like a piece of code (which is, actually) than a visual representation of the interface. For some developers this is a plus, but for hybrid designers/developers, having a template makes it <strong>easier to think in terms of design and CSS</strong>. Vue pays the price of a lightweight data link DSL (Domain Specific Language) so that you have a visually scannable template with encapsulated logic and directives.</p><p>Another problem with React is that DOM updates are fully delegated to the virtual DOM. That is a bit complex if you need to control the DOM directly (although you can, if you do it you’re essentially roaming against the principle of the library itself). For applications that require <strong>custom DOM manipulations</strong>, like animations with special synchronization needs, this may be a particularly annoying restriction. On this front, Vue allows more flexibility — and there are numerous FWA/Awwwards winning sites built with VueJS.</p><h3>Additional notes:</h3><ul><li>The React team has very ambitious goals to make React an agnostic UI development platform paradigm, while<strong> Vue is more geared to providing a pragmatic solution</strong> to the web.</li><li>React, because of its functional nature, works very well with functional programming models. However, this also introduces a higher learning curve for young and beginner developers. Vue is much <strong>easier to learn and this makes it more productive</strong> in this regard.</li><li>For large applications, the React community has done a lot in terms of state control solutions, e.g. Flux / Redux. Vue alone does not aim to solve that problem (it is the same for the React core), but state management models can be easily adopted for a similar architecture. <strong>Vue has its own unique status management system called Vuex</strong>, and you can also use Redux with Vue.</li><li>The development in <strong>React encourages you to enter everything in JavaScript</strong>, including your CSS. There have been many CSS-in-JS solutions here but more or less all have their problems. And more importantly, this diverges from the classic CSS production experience and makes it very uncomfortable to take advantage of the existing CSS community work. Single-file components provide you with CSS encapsulated in components while allowing you to use your favorite pre-processor.</li></ul><p><em>This post first appeared on </em><a href="https://www.monksoftware.it/blog/vuejs-explained-in-ten-minutes/"><em>monksoftware.it</em></a><em>. Author: Agostino Convertini, Front-End Developer.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f924fb1c581" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[With conversational interfaces, content is turning into a big thing]]></title>
            <link>https://medium.com/@monksoftware/with-conversational-interfaces-contents-are-turning-into-a-big-thing-46871bc841e9?source=rss-28dd4b33af4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/46871bc841e9</guid>
            <category><![CDATA[marketing-technology]]></category>
            <category><![CDATA[content-marketing]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[instant-messaging]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <dc:creator><![CDATA[MONK Software]]></dc:creator>
            <pubDate>Thu, 08 Jun 2017 09:35:29 GMT</pubDate>
            <atom:updated>2017-06-21T09:41:55.588Z</atom:updated>
            <content:encoded><![CDATA[<p>Not that it wasn’t before, of course. Nobody can deny it: since the boom of social networks and storytelling, this is content marketing’s golden age.</p><p>In the past few years I have worked with content quite a lot — coping with newsletters, SEO and corporate blogs. I often found myself wondering how such marketing approach could evolve in the future. And I remember the exact moment when I realized <strong>everyone had an opinion about content marketing</strong>. It seemed like a saturation to me, which led me to question the trend in the long run.</p><p>Then, I joined <a href="http://www.monksoftware.it/">Monk Software</a>. And I had to face one of the biggest changes of our super-hectic days: <a href="http://www.monksoftware.it/blog/instant-messaging-apps-customer-care/">the conversational paradigm</a>. That’s a huge topic to discuss about. Though, to some extent, that can also be described as the transition <strong>from Graphic User Interfaces</strong> (GUI) <strong>to Conversational Interfaces</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*89kl4bOsDu682VCT.jpg" /></figure><p>A revolution? On the one hand, yes. It <em>is</em> a revolution. It is because of the way this is happening — just think of chatbots and voice assistants. On the other hand, not really. Conversational interfaces are just making a come-back.</p><p>A bit of history may be of help to understand why and how.</p><h3>Conversational interfaces: from ELIZA to Siri</h3><p>GUI (Graphic User Interfaces) were born in the ’80s to Xerox. From Lisa on, Steve Jobs has somehow disclosed their potential. But the ancestors of <strong>conversational interfaces were there far before</strong> Xerox invented its own GUI. <a href="https://medium.com/conversational-interfaces/conversational-interfaces-arent-new-but-they-re-changing-the-game-67578e37ac3">Just think of ELIZA</a>, created in the ’60s: it was so impressive it looked like it just came out of a dystopia.</p><p>Keeping it outrageously simple, one could say conversational interfaces gave way to GUIs mainly because of the medium itself. Conversations were definitely not the best way to interact with a personal computer. A screen with a keyboard and a mouse just shout “look at me” and “click here”.</p><p>A couple decades later (<em>with a number of new technologies and approaches in the middle</em>), smartphones industry exploded. A mass product completely different from a regular phone, and still not really a computer. Once again, <strong>the medium required a step forward</strong> — or a step behind — <strong>in UX</strong>. How to give a “hybrid phone” a user-friendly interface? The most logical answer was “conversations”. Or, at least, some kind of interface including conversations.</p><p>Sooner than we think, we will expect interacting with phones like with a concierge. Not a coincidence that 2017 is all about “AI First” to many companies .</p><h3>Conversational and content marketing</h3><p>Natural language processing is the new hot topic. So are artificial intelligences, especially on mobile. And this is just the start.</p><p>Still, no one can really believe consumers are going to feel totally comfortable interacting with a robot all of a sudden. There’s the need for an intermediary step, for a soft transition. <strong>Instant messaging, for example, is something in-between edge technology and old-fashioned chat</strong> models like IRC. People love chatting, they know how to do it, they do it using their natural language. Well, through instant messaging they can easily do it from their smartphones.</p><p>I know what you are thinking: what the heck does all this have to do with content marketing? A lot, trust me. Bots, instant messengers &amp; co. are a new medium, and the properties of the medium itself are leading to the transformation of content marketing into conversational marketing. <strong>Storytelling needs to adapt to the context</strong>.</p><p><strong>A well-designed artificial intelligence</strong> — or a chat, with or without a bot — <strong>should always tell a story</strong>, consistent with its primary purpose or with the storytelling of the company it represents. In other words, it should have a soul — of bits, but still a soul. First of all ’cause no one has a desire for conversation with a robot that <em>sounds</em> like a robot. Second of all, because it’s a terrific opportunity for brands.</p><p>Let’s play a game. Take your iPhone and ask Siri “What’s the best phone?”. Strange as it may seems, <em>her</em> answer will state in just 3 words Siri’s personality Apple’s positioning and tone of voice.</p><h3>Instant messaging as a head start</h3><p>Face it: content is never going to be the same, and it’s for the better. It won’t be (or won’t just be) on HTML pages of static blogs. It won’t be only GIFs and videos, but conversation in the making. That’s <strong>the missing piece of the content marketing puzzle</strong>: conversational marketing. Here, companies are going to play their biggest games.</p><p>Any given paradigm,though, requires <strong>an intermediate step</strong> to let people get used to it. We think instant messaging is the key for companies to make this change, giving them a head start in the <strong>conversational paradigm</strong>. And we believe it’s even more important when it comes to educate consumers to new ways of interacting with brands — and to engage them, nonetheless. Our experience, so far, has proven us right. That’s why we created <a href="http://eime.monksoftware.it/"><strong>EIMe</strong>, <strong>our Enriched Instant Messaging</strong></a><strong>.</strong></p><p><em>This post was originally published at </em><a href="http://www.monksoftware.it/blog/conversational-interfaces-content-marketing/"><em>www.monksoftware.it</em></a><em> by Sara Squintu</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46871bc841e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started With Vapor 2 — Restful API Swift Server]]></title>
            <link>https://medium.com/@monksoftware/getting-started-with-vapor-2-restful-api-swift-server-bcd5c15fe2ba?source=rss-28dd4b33af4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcd5c15fe2ba</guid>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[vapor]]></category>
            <category><![CDATA[restful]]></category>
            <dc:creator><![CDATA[MONK Software]]></dc:creator>
            <pubDate>Thu, 01 Jun 2017 08:27:49 GMT</pubDate>
            <atom:updated>2017-06-20T16:58:25.643Z</atom:updated>
            <content:encoded><![CDATA[<p>As previously announced <a href="https://medium.com/@qutheory/vapor-2-less-code-more-power-af1e1ec5affa">here</a>, Vapor framework has just rolled out it’s 2.0 version. Here at Monk Software, we are always looking for new technologies, and we gave Vapor a chance!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/913/0*hxHP3L1Q_7taa2dj.jpg" /><figcaption>Vapor 2.0 — a web framework for Swift</figcaption></figure><h3>What is Vapor?</h3><p>Vapor is a server-side Swift web framework. Whatever your needs are, Restful API Server, display html pages, send emails or push notifications, Vapor will suite almost everything.</p><h3>What we are going to cover in this blog post?</h3><p>Today, I wanna show you how easy it is for you to start with a Vapor API template, add some endpoints and then deploy your server to Heroku.</p><h3>Let’s get started</h3><p>I assume you are on a Mac with Swift &amp; Xcode installed, if not, please install <a href="https://developer.apple.com/xcode/">Xcode</a> (Swift it’s bundled inside), if you are on Ubuntu, please follow this <a href="https://docs.vapor.codes/2.0/getting-started/install-on-ubuntu/">guide</a> to get started.</p><p>1) Install Vapor Toolbox</p><p>To take full advantage of Vapor, we need also it’s toolbox, you can install by typing in your terminal:</p><pre>brew install vapor</pre><p>or if you are in ubuntu, this:</p><pre>sudo apt-get update <br>sudo apt-get install vapor</pre><p>2) Create a new app</p><p>Create an app it’s super simple, just type in your terminal:</p><pre>vapor new IncredibleVaporApp --template=api (or whatever name you want)</pre><p>In a few, Vapor should download all dependencies and create a folder with given app name.</p><p>3) Optional: Generate Xcode project file</p><p>If you want to take advantage of Xcode autocompletion, you can type this in terminal inside your vapor app folder:</p><pre>vapor xcode</pre><p>this will generate .xcodeproj, type ‘y’ to open in Xcode.</p><p>4) Run server</p><p>Ok, we are ready to run our server, if you use Xcode, select scheme <strong>App </strong>and press play, if you are in Ubuntu, type in terminal:</p><pre>vapor build &amp;&amp; vapor run</pre><p>build will extract a build to be deployed, than run will start your server.</p><p>Vapor will start server by default at this address:<strong> </strong><a href="http://0.0.0.0:8080/"><strong>0.0.0.0:8080</strong></a>, to test, go to <a href="http://0.0.0.0:8080/hello,"><em>http://0.0.0.0:8080/hello,</em></a><em> </em>you will see a json of this type:</p><pre>{&quot;hello&quot;:&quot;world&quot;}</pre><p>Everything works as expected!</p><p>5) Add custom endpoint</p><p>It’s time to add our custom endpoint, let’s say we want to greet a person by passing in URL his name. First of all, open <strong>Routes.swift</strong> file in our project, then, in method</p><pre>func build(_ builder: RouteBuilder) throws</pre><p>we can add our new API:</p><pre>builder.get(&quot;greet&quot;) { req in</pre><pre>    let name = req.data[&quot;name&quot;]?.string ?? &quot;, what&#39;s your name? :D&quot;</pre><pre>    return &quot;Hello \(name)&quot;<br>}</pre><p>This code simply does two things, adds new API to endpoint <strong>0.0.0.0:8080/greet</strong>, than check if there is in the URL a parameters called <strong>“name”</strong>, if present, it will return a string “Hello” with the name provided, if not, it will ask you what’s your name, simple as that. Save and re-run our server by pressing play in Xcode.<br>Navigate to <strong>0.0.0.0:8080/greet</strong> and press enter, the result should be:</p><pre>Hello , what&#39;s your name? :D</pre><p>And of course, passing a valid name like this <strong>0.0.0.0:8080/greet?name=Alessio</strong> will result in:</p><pre>Hello Alessio</pre><p>6) Push to Heroku</p><p>We created our first server and we want to greet everyone in the world! Heroku will help us. Open terminal in the root folder of the project and type:</p><pre>vapor heroku init</pre><p>if you are not logged to heroku you will be prompted in to login; than heroku will ask for a custom name, we are living it empty, so type ’n’, than, at the question:<br>“Would you like to deploy to other than US region server?” type <strong>‘n’</strong>,</p><p>“Would you like to provide a custom Heroku buildpack?” type <strong>‘n’,</strong></p><p>“Are you using a custom Executable name?” type <strong>‘n’</strong>,</p><p>“Would you like to push to Heroku now?” type <strong>‘y’. </strong>(This will take 5~10 mins). When finished heroku will give you with git endpoint of project and an http URL, copy paste that URL in a browser and add our custom endoint like this (mine is <a href="https://shrouded-fjord-73521.herokuapp.com/):">https://shrouded-fjord-73521.herokuapp.com/):</a></p><pre><a href="https://shrouded-fjord-73521.herokuapp.com/greet?name=alessio">https://shrouded-fjord-73521.herokuapp.com/greet?name=alessio</a></pre><p>Everything should work like local server.</p><p>Congratulations, you have just created and deployed a Restful Vapor Swift server in the cloud! Hope you enjoyed this tutorial, more will come soon!</p><p><em>This tutorial was originally published on </em><a href="http://www.monksoftware.it/blog/vapor-2-restful-api-swift-server/"><em>MONK Software’s blog, by Alessio Arsuffi</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcd5c15fe2ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Reasons to Choose an Open Source ERP]]></title>
            <link>https://medium.com/@monksoftware/5-reasons-to-choose-an-open-source-erp-b6c7a8a040aa?source=rss-28dd4b33af4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6c7a8a040aa</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[odoo]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[erp]]></category>
            <dc:creator><![CDATA[MONK Software]]></dc:creator>
            <pubDate>Wed, 24 May 2017 11:53:59 GMT</pubDate>
            <atom:updated>2017-06-20T16:59:27.690Z</atom:updated>
            <content:encoded><![CDATA[<p>Your company is growing: orders increase, you are hiring more people, the warehouse is getting bigger. It’s getting harder and harder to keep track of everything through post-its strewn all over the office, or through the large spreadsheet you have so carefully built during the past few months.</p><p>If you ever find yourself in this situation, it means it’s <strong>time for you to start using an ERP software</strong>.</p><p>The initial investment may seem steep, but the value provided should exceed it tenfold, if it’s implemented and used correctly.</p><p>Let’s assume you’ve had a life revelation and decided to invest in an ERP. Now the question is: which one?<br>You google it and find out immediately there are plenty of choices and options to choose from. SaaS or on premise? Big general-purpose or something more focused? <strong>Open Source or Closed Source</strong>?</p><p>This last question may be one few people reflect on, but I feel like that choice is more important — and has more consequences — than most people realize.</p><p>In this article I hope I can show you the reason why I feel opting for an Open Source ERP may be the right way to go.</p><p>First, let me set the record straight on some common misconceptions:</p><ul><li><strong>Open Source does not mean “for free”</strong>, nor cheap. Open source ERP — and software in general — can cost much less or much more than similar Closed Source alternatives.</li><li><strong>Open Source does not equal shoddy, “amateurish” or “second-class” software</strong>. There is this myth that all the Open Source software have been written by a bunch of young developers in their free time as a hobby. The reality is that a lot of Open Source software are created and/or backed by major corporations and foundations like Google, Red Hat, Facebook, Microsoft or — to cite some “smaller” names in the enterprise software space — Odoo (300 employees, 2 million users) and Magento (500–1000 employees, hundreds of thousands of stores using it).</li></ul><p>Having said that, let’s dive right in and take a look at 5 major advantages granted by Open Source ERPs!</p><h3>1. No vendor lock-in</h3><p>Imagine you find a Closed Source ERP that offers you a great solution at a very attractive cost. You opt for it, and for the first few months everything seems to be great!</p><p>Now, the software house needs to make money and decides that, starting from the next year, some of the features you are currently using will turn into very expensive add-ons. And you have no will to pay so much for them. Surprise! As you have no control over the software, there’s not much you can do. You’ll just have to stop using those features.</p><p>This is a common trait of most — if not all — Closed Source solutions: the <strong>company which writes the software</strong> has a complete control over your installation. You may have your own a database containing all of your data, but<br>those are useful only thanks to the ERP. In fact, having the data without a software applying logics to them,<br>means you are basically back to the old post-its or to the large spreadsheet. And, as long as you know, the ERP<br>is a big black box — you can’t look into it and see how it works.</p><p>With an open source ERP, you’ll always have access to the “box” you’re using, and it’s not black, it’s transparent: <strong>you can see every part of it</strong>. How it works, how it uses your data. This serves as an insurance and gives the control over your installation back to you.</p><h3>2. Extensibility</h3><p>With an Open Source ERP, you have <em>full access to the source code</em>. That means you can <strong>change and customise every single aspect or function of the software</strong>, not just what the software provider thought about or allowed you to change.</p><p>It’s not unlikely having your own home vs renting. Sure, in your rented home you can change the carpet, maybe even repaint the walls in the colors you want.<br>But with an Open Source ERP you are free to literally tear down the walls between the kitchen and the living room and create the open-concept kitchen you’ve always dreamed of.</p><p>Metaphors aside, <strong>we at MONK Software use an Open Source ERP</strong> to manage all of our enterprise processes: sales, accounting, project management, employees management.</p><p>We could’ve done the same with most ERPs, either Closed or Open Source, but only by exploiting the superior extensibility of our choosen Open Source ERP we were enabled to do some of “heavier” customisations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jiaIx3U6cSOUpRpV.png" /><figcaption>MONK Software’s Odoo</figcaption></figure><p>Our heavily customised Odoo; you can see in the top right the lunch counter</p><p>We currently use it as <strong>datasource for our smart office</strong>. We overhauled the UI to match our needs and brand identity, and developed ad hoc modules to manage stuff you wouldn’t find in any other ERP. For example, we now track who’s there for lunch so that our in-house “chef” knows how many people she needs to cook for :D</p><p>Also, we are in the process of integrating <a href="http://eime.monksoftware.it/">EIMe, our great conversational solution</a> into the ERP to facilitate intra-company communications!</p><h3>3. Quality of the code</h3><p>This one isn’t an intrinsic advantage of Open Source software, but rather a common consequence.</p><p>Because it will be <strong>publicly visible</strong>, developers are motivated to write a cleaner, well-commented, easier to understand and all-around better code.</p><p>They’ll tend to avoid poor-quality code, makeshift solutions or any other piece of suboptimal code that you wouldn’t want powering the software that manages your entire company.</p><p><strong>For software developers, code is like a portfolio</strong>. Nobody wants their name associated with a bad piece of code, just like no construction company would want to put their name on a collapsing, ugly building.</p><p>This is not to say that Closed Source code always has a lower quality. Companies usually have internal practices and guidelines to write good code, and with no doubt there are Closed Source software with quality, well-commented code.</p><p>The thing is with a Closed Source software you have to trust in the company practices to enforce good-quality code. With an Open Source software <strong>you can assess the code quality yourself</strong> (or ask your developers to do so) and trust in the constant public scrutiny that pushes developers to write only acceptable code.</p><p>Being a coder myself, I can promise you that even if I try to always write code as good as<br>possible, making it public always stimulates me to check it and make sure it all looks good (if you are interested, <a href="https://github.com/monksoftware">you can find our public stuff on github</a>).</p><h3>4. Security</h3><p>A lot of people believe that being Open Source equals being less secure, because everyone can “look under the hood” and look for potential vulnerabilities.</p><p>This is a common myth that, despite being disproven over and over again, is still prevalent in the minds of non-technical people.</p><p>There is this mantra in the security community that “<a href="https://en.wikipedia.org/wiki/Security_through_obscurity">security through obscurity</a> is not security at all.”</p><p>So, the truth is the opposite: for similar reasons to the one of my previous point, <strong>Open Source code is often more secure than Closed-Source</strong> equivalents.</p><p>The <a href="https://courses.cs.washington.edu/courses/csep590/05au/whitepaper_turnin/oss(10).pdf">University of Washington did one of several studies</a> on the subject, coming to this conclusion:</p><blockquote><em>Open source does not pose any significant barriers to security,<br>but rather reinforces sound security practices by involving many people<br>that expose bugs quickly, and offers side-effects that provide customers and the<br>community with concrete examples of reusable, secure, and working code.</em></blockquote><h3>5. Community</h3><p>Last but not least, an Open Source ERP, as any Open Source software, <strong>attracts an opensource-friendly</strong><br><strong>community</strong>. This means there usually is a spirit of collaboration, teamwork and participation that encourages<br>people to contribute in many ways.</p><p>As a consequence, the number of users reporting bugs, proposing features and ideas and generally contributing is higher than usual.</p><p>In addition to that, in case of bugs or any other issue that may be blocking for your business, <strong>you can fix the problem yourself and even share the fix with the whole community</strong>, with no need to report the issue and waiting for someone else to solve it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/0*Rt8s582A2FgGmsCG.png" /><figcaption>Odoo Community</figcaption></figure><p>Odoo community on github in numbers: 6100+ stars, 5700+ forks, 2400+ open user reports, 900+ open user-proposed patches.</p><p>Does it sound rare and unlikely?</p><p>Well, I — as part of my work at MONK Software — have <a href="https://github.com/odoo/odoo/issues?utf8=%E2%9C%93&amp;q=author%3ALeartS">reported and fixed multiple bugs in Odoo</a>, and they accepted and incorporated my patches.</p><p>This means MONK Software and I are officially contributors to Odoo’s source code. Pretty cool!</p><h3>Conclusions</h3><p>I think most of the article comes down to this:</p><ul><li>With an Open Source ERP, <strong>you can be more pro-active</strong> regarding your ERP implementation.</li><li>By contrast, with a Closed Source ERP, you can’t help but accept the decisions of the software creators and hope they matches your needs!</li></ul><p>If you want to know more about how an <strong>Open Source ERP can be useful</strong> for your company, <a href="http://www.monksoftware.it/contact/">contact us</a>!</p><p><em>This post first appeared </em><a href="http://www.monksoftware.it/blog/reasons-to-choose-an-open-source-erp/"><em>on MONK Software’s blog, by Leonardo Donelli</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6c7a8a040aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AASheetController: UIImagePickerController with embedded photoLibrary]]></title>
            <link>https://medium.com/@monksoftware/aasheetcontroller-uiimagepickercontroller-with-embedded-photolibrary-b4650def5f2d?source=rss-28dd4b33af4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4650def5f2d</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[cocoapods]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[MONK Software]]></dc:creator>
            <pubDate>Wed, 10 May 2017 11:55:49 GMT</pubDate>
            <atom:updated>2017-05-10T11:55:49.929Z</atom:updated>
            <content:encoded><![CDATA[<p>At MONK Software, we strongly believe in collaborative software. Open Source community is something great and so huge that we just want to say thanks to everyone out there who keeps doing great projects/libraries &amp; blog articles. Thanks for sharing!</p><p>During our latest iOS project, we needed something that Apple’s APIs don’t provide. We were searching for a sort of <strong>UIImagePicker</strong> with an embedded <strong>photo library</strong>, but we were unable to find something that would have suited our needs. So we just thought it would have been great to create something ad hoc for us and obviously share it this new component with the community and, just as obviously, release it Open Source.</p><h3>AASheetController</h3><p>It is an <a href="https://developer.apple.com/reference/uikit/uiimagepickercontroller">UIImagePickerController</a> based component, but it adds capability to show <strong>photo library</strong> of our iDevices!</p><p>It is written in pure Swift 3 and it relies on <strong>Photos.framework</strong> provided by Apple. It is distributed under the <a href="https://github.com/alessioarsuffi/AASheetController/blob/master/LICENSE">MIT</a> licence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/180/0*3APDoWhvqZOUbUD6." /><figcaption>AASheetController</figcaption></figure><p>We choose <a href="https://github.com/alessioarsuffi/AASheetController">Github</a> &amp; <a href="https://cocoapods.org/pods/AASheetController">Cocoapods</a> to distribute our library. Github because it’s the most popular open source site <em>(AFAIK)</em>, and Cocoapods because it’s the <strong><em>de facto</em></strong> dependency manager in iOS.</p><h3>Show me code!</h3><p>Ok so, we are nerds, we write code! Show me code!<br>…well, You can read documentation…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*JFQGZUgLwEbYGbrT.jpg" /></figure><p>AASheetController</p><p>I was joking man!<br>However documentation is pretty straightforward :)</p><p>to install library open your <strong>Podfile </strong>and add:</p><pre>pod &quot;AASheetController&quot;</pre><p>then, into a terminal shell, at the root of your iOS project, type:</p><pre>pod install</pre><p>this will download library. Now open Xcode, open a file and import library:</p><pre>import AASheetController</pre><p>this will let you access custom component, now create it by typing:</p><pre>let sheetController = AASheetController(barButtonItem: nil)</pre><p><strong>NB:</strong> in case you are displaying it for <strong>iPad</strong>, you should pass <strong>barButtonItem</strong> so controller will anchor to that.</p><p>If you prefer to hide cancel button at the bottom add:</p><pre>sheetController.showCancelButton = false</pre><p>if you don’t want to show photoLibrary:</p><pre>sheetController.showCollectionView = false</pre><p>the only thing which is requested is to add this line into Info.plist file of your project:</p><pre>Privacy - Media Library Usage Description with a message you prefer (ex. We access photo library to share images on social networks)</pre><p>That’s it, I hope you will enjoy this simple library. In case you have any doubts or requests, feel free to reply to this blog post or post a new issue on <a href="https://github.com/alessioarsuffi/AASheetController/issues">Github</a>.</p><p><em>This blogpost was originally published on </em><a href="http://www.monksoftware.it/"><em>www.monksoftware.it</em></a><em> by Alessio Arsuffi</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4650def5f2d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Instant Messaging is the new black]]></title>
            <link>https://medium.com/@monksoftware/instant-messaging-is-the-new-black-d34f1dbf8c5e?source=rss-28dd4b33af4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d34f1dbf8c5e</guid>
            <category><![CDATA[conversational]]></category>
            <category><![CDATA[software-house]]></category>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <dc:creator><![CDATA[MONK Software]]></dc:creator>
            <pubDate>Wed, 03 May 2017 12:23:47 GMT</pubDate>
            <atom:updated>2017-05-10T10:29:47.124Z</atom:updated>
            <content:encoded><![CDATA[<p>According to the <a href="http://www.slideshare.net/wearesocialsg/digital-in-2017-global-overview">latest data released by WeAreSocial</a>, <strong>2.8 billion people use social networks</strong> at least once month — and almost all of them (2.4 billions) do it from their smartphones. This no longer is a surprise. However, what is mostly disruptive is the change social media are currently experiencing. In no time, stream walls and public posts are running out of fashion.</p><p>Though Facebook still tops the list as the most used social platforms, Zuckerberg has clearly put his heart (and wallet) into <strong>instant messaging apps</strong>. WhatsApp and FB Messenger (followed by QQ, WeChat and a number of other lesser-known ones), proved once more to be the users’ favourite apps leaving Twitter, YouTube and even Instagram behind in terms of loyalty and engagement.</p><h4>Conversational first</h4><p>This now obvious reality reflects two trends which started already some time ago: from one side, the users’ growing need for intimate and more direct channels; from the other, the increasing importance of <strong>natural language processing </strong>and <strong>Conversational User Interfaces (CUI)</strong>.</p><p>In terms of UX, Instant Messaging apps require a <strong>very lowf learning curve</strong>. They are so intuitive that even your mom — or that uncle of yours who just can’t get technology right — use them on a daily basis.</p><p>It’s no surprise then, that companies and corporations all over the world — like <a href="http://www.forbes.com/sites/rachelarthur/2016/03/30/sephora-launches-chatbot-on-messaging-app-kik/#7205267b512c">Sephora</a> and <a href="http://uk.businessinsider.com/taco-bells-tacobot-orders-food-for-you-2016-4?r=US&amp;IR=T">TacoBell</a>, just to name a few — have acknowledged the big success of Instant Messaging and are looking for ways to leverage on it just as they were doing with social networks a few years earlier.</p><p>Most of them are focusing on the development of <strong>Chatbots</strong> for existing Instant Messaging apps. Just a few are so visionary to engage directly into <strong>XMPP</strong> to create their own IM premise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*uGKYuK5LpXlTeICx.jpg" /></figure><h4>Three opportunities for Customer Service</h4><p>Customer Care is the first and most obvious business process where companies can harvest the benefits of creating a one-to-one relationship with clients in their comfort zone.</p><h4>1. Natural Interaction</h4><p>Consumers can interact with brands <strong>as they do with their friends and family</strong>, using natural language. Without leaving the conversational context, they can also <strong>receive and send</strong> a variety of attachments (photos, videos, documents) to get their case through — reinforcing, as a result, the effectiveness of interactions. This is an advantage for companies, too.</p><h4>2. Asynchronicity</h4><p>Moreover, Instant Messaging does not create real-time service expectations. On live chats (or phone call-centers), we anxiously wait for an answer also fearing to lose our turn, whilst Instant Messaging apps typically allows us to carry on with our business as long as a push notification alerts us there is a reply. For companies, asynchronicity translates into a <strong>more efficient peak management</strong> and into reducing customer frustration.</p><h4>3. Lower call-back rates</h4><p>Instant Messaging, as opposed to life chats or standard apps, brings about another great advantage for both customers and companies: <strong>easy retrievable information</strong>. Whatever info you may have asked for, you can look them up in the thread with Customer Support. This reduces the call-back rates. For customers it means <strong>better service</strong> and for companies more savings.<br>No less, for companies the threads between customers and Customer Support represent a very valuable source of <strong>qualitative and quantitative information</strong> to be used for improving processes and enhancing machine learning algorithm.</p><h4>Not all Instant Messaging apps are equals</h4><p>Some popular Instant Messaging apps are more open than others. The<strong> degree of customization</strong> they offer to businesses is however inherently limited by the very nature which made them huge: the focus on facilitating person to person interaction. We, in MONK Software, have developed EIMe (Enriched Instant Messaging) to respond to opportunities for greater value companies could harvest from natural language paradigm. By no means we’re aiming to compete with the giants of p2p Instant Messaging, but we believe a well tailored solution (and an own premise) can enable a more effective relationship between companies and their customers.</p><p>To find out more, <a href="http://eime.monksoftware.it/">meet EiME here</a>.</p><p><em>This article first appeared on </em><a href="http://www.monksoftware.it/"><em>www.monksoftware.it</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d34f1dbf8c5e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>