<?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 Bart Ozdoba on Medium]]></title>
        <description><![CDATA[Stories by Bart Ozdoba on Medium]]></description>
        <link>https://medium.com/@bart_oz?source=rss-baceef3e1737------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*N6QfOBc1cdRuFAhjPP3WBQ.png</url>
            <title>Stories by Bart Ozdoba on Medium</title>
            <link>https://medium.com/@bart_oz?source=rss-baceef3e1737------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:17:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bart_oz/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[UUID’s in Rails + SQLite shouldn’t be this hard (so I built a gem)]]></title>
            <link>https://medium.com/@bart_oz/uuids-in-rails-sqlite-shouldn-t-be-this-hard-so-i-built-a-gem-63f56a4a3bd9?source=rss-baceef3e1737------2</link>
            <guid isPermaLink="false">https://medium.com/p/63f56a4a3bd9</guid>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[uuid]]></category>
            <category><![CDATA[rubygems]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[sqlite]]></category>
            <dc:creator><![CDATA[Bart Ozdoba]]></dc:creator>
            <pubDate>Mon, 22 Dec 2025 12:07:37 GMT</pubDate>
            <atom:updated>2025-12-22T13:24:00.342Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*OKbosXUXtYMvlMZuP55yTA.jpeg" /></figure><p><strong>tl;dr</strong> — If you just want UUIDs or ULIDs working in your Rails + SQLite app:</p><pre># Gemfile<br>gem &quot;sqlite_crypto&quot;</pre><pre># migration<br>create_table :users, id: :uuid do |t|<br>  t.string :email<br>  t.timestamps<br>end</pre><p>That’s it. Foreign keys auto-detect, schema.rb stays clean, everything just works. Feel free to try it, it’s MIT licensed.</p><p><a href="https://github.com/bart-oz/sqlite_crypto">Github</a> | <a href="https://rubygems.org/gems/sqlite_crypto">RubyGems</a></p><h3>The Problem I Hit with using UUID’s with SQLite</h3><p>I was building a Rails 8 app with SQLite-embracing the “No PaaS Required” philosophy that DHH articulated in the Rails 8 release. SQLite as a production database finally felt real: WAL mode (Write-Ahead Logging) by default, improved busy handlers, the Solid Stack proving it at scale.</p><p>Then I needed UUID primary keys.</p><p>In PostgreSQL, this is a one-liner: enable_extension &#39;pgcrypto&#39; and you&#39;re done. In SQLite? I fell into a rabbit hole.</p><h4>What went wrong</h4><p>First of all my schema.rb broke immediately. Rails dumped something like this:</p><pre>create_table &quot;users&quot;, id: false, force: :cascade do |t|<br>  t.string &quot;id&quot;, limit: 36, null: false<br>  # ...<br>end</pre><p>Not id: :uuid. A verbose, non-reloadable mess.</p><p>Foreign keys became a nightmare. When I added a posts table with t.references :user, Rails created an INTEGER column. My UUID primary key and integer foreign key couldn&#39;t join. Every single reference needed manual type: :string, limit: 36 configuration.</p><p>User.first returned random records.* UUID v4 is randomly ordered, so &quot;first&quot; meant alphabetically first, not chronologically first. I learned about implicit_order_column the hard way.</p><h4>What I had to implement manually</h4><ol><li><strong>Verbose migration syntax with </strong><strong>id: false:</strong></li></ol><pre>create_table :users, id: false do |t|<br>  t.string :id, limit: 36, null: false, primary_key: true<br>  t.string :email<br>  t.timestamps<br>end</pre><p>Instead of the clean id: :uuid I wanted.</p><p><strong>2. Manual type specification on every foreign key:</strong></p><pre>create_table :api_keys, id: false do |t|<br>  t.string :id, limit: 36, null: false, primary_key: true<br>  t.references :user, null: false, foreign_key: true, type: :string, limit: 36<br>  # ...<br>end</pre><p>Forget type: :string, limit: 36 once? Broken joins. That might lead to silent failures and hours of debugging.</p><p><strong>3. Custom UUID generation in ApplicationRecord:</strong></p><pre>class ApplicationRecord &lt; ActiveRecord::Base<br>  primary_abstract_class<br>  <br>  before_create :generate_uuid_id<br>  <br>  private<br>  <br>  def generate_uuid_id<br>    self.id ||= SecureRandom.uuid<br>  end<br>end</pre><p><strong>4. Special handling for Active Storage:</strong></p><p>Active Storage tables don’t inherit from ApplicationRecord, so they needed their own initializer:</p><pre># config/initializers/active_storage_uuid.rb<br>Rails.application.config.to_prepare do<br>  ActiveStorage::Blob.class_eval do<br>    before_create { self.id ||= SecureRandom.uuid }<br>  end<br>  # ... repeat for Attachment, VariantRecord<br>end</pre><p><strong>5. The schema format tradeoff:</strong></p><p>Many tutorials suggested switching to structure.sql:</p><pre># config/application.rb<br>config.active_record.schema_format = :sql</pre><p>This “solved” the schema.rb dump problem but introduced others: SQL format, which is database-specific, harder to diff in PRs, and doesn’t play as nicely with some deployment pipelines. I wanted to keep :ruby format.</p><p>All of this boilerplate for something that PostgreSQL handles with a single enable_extension &#39;pgcrypto&#39;.</p><h4>What I tried</h4><ul><li><strong>One popular gem</strong> hadn’t been updated since 2015 — ten years of Rails versions unsupported</li><li><strong>Several options</strong> required manual id: false configuration and didn&#39;t handle foreign keys</li><li><strong>One promising gem</strong> was still in alpha and required external SQLite extension management</li></ul><p>The common pattern: solutions existed, but none provided the complete package. I wanted something that felt as natural as PostgreSQL’s UUID support-install the gem, use id: :uuid, and forget about it.</p><h4>But why UUIDs/ULIDs Matter (A Quick Primer)</h4><pre>Type      Example                              Characteristics<br>────────  ───────────────────────────────────  ─────────────────────<br>INTEGER   1, 2, 3, ...                         sequential, guessable<br>UUID      550e8400-e29b-41d4-a716-446655440000 random, 36 chars<br>ULID      01ARZ3NDEKTSV4RRFFQ69G5FAV           time-sortable, 26 chars</pre><p><strong>Security</strong>: Sequential IDs leak information. If your user ID is 47, attackers know there are ~47 users and can enumerate /users/1 through /users/47. UUIDs are effectively unguessable.</p><p><strong>Distributed systems</strong>: Integer IDs require a central authority to prevent collisions. UUIDs can be generated anywhere-your server, a client device, an offline app-without coordination.</p><p><strong>ULID advantage</strong>: Unlike random UUIDs, ULIDs encode creation time. User.first returns the oldest record, not a random one. You get security benefits while preserving intuitive ordering.</p><p><strong>The tradeoff</strong>: UUIDs use 36 bytes vs 8 bytes for integers. Queries are ~2–5% slower from my performance testing. For most applications, this is negligible. For write-heavy analytics tables processing millions of rows per hour, you might want to stick with standard incremented ID’s.</p><h4>Performance Reality Check</h4><pre>Operation                    Integer   UUID      ULID<br>───────────────────────────  ────────  ────────  ────────<br>Insert 10k records           baseline  +3-5%     +5-8%<br>Find by ID (1k lookups)      baseline  +2-4%     +3-5%<br>Where queries                baseline  ~same     ~same<br>Storage per 1M records       ~8 MB     ~34 MB    ~25 MB</pre><h4>My Solution: sqlite_crypto</h4><p>I built sqlite_crypto to make UUID/ULID primary keys feel native in Rails + SQLite.</p><p><strong>Installation:</strong></p><pre># Gemfile<br>gem &quot;sqlite_crypto&quot;</pre><pre>bundle install</pre><p>No generators. No configuration files. No initializers.</p><p><strong>UUID Primary Keys usage:</strong></p><pre>class CreateUsers &lt; ActiveRecord::Migration[8.0]<br>  def change<br>    create_table :users, id: :uuid do |t|<br>      t.string :email<br>      t.string :name<br>      t.timestamps<br>    end<br>  end<br>end</pre><p><strong>ULID Primary Keys (Time-Sortable) usage:</strong></p><pre>class CreatePosts &lt; ActiveRecord::Migration[8.0]<br>  def change<br>    create_table :posts, id: :ulid do |t|<br>      t.string :title<br>      t.text :content<br>      t.timestamps<br>    end<br>  end<br>end</pre><p><strong>Automatic Foreign Key Detection:</strong><br>This is the feature I’m most proud of. The gem inspects the referenced table’s primary key and creates matching foreign keys automatically:</p><pre># Users has UUID primary key<br>create_table :users, id: :uuid do |t|<br>  t.string :name<br>end<br><br># Posts automatically gets varchar(36) user_id — no manual type: needed!<br>create_table :posts do |t|<br>  t.references :user  # Just works™<br>  t.string :title<br>end</pre><p><strong>Works with ULID too:</strong></p><pre>create_table :categories, id: :ulid do |t|<br>  t.string :name<br>end<br><br>create_table :articles do |t|<br>  t.references :category  # Creates varchar(26) foreign key<br>  t.string :title<br>end</pre><p>For non-standard table names, use :to_table:</p><p><strong>Clean Schema Output<br></strong>Your db/schema.rb stays readable:</p><pre>create_table &quot;users&quot;, id: :uuid, force: :cascade do |t|<br>  t.string &quot;email&quot;<br>  t.datetime &quot;created_at&quot;, null: false<br>  t.datetime &quot;updated_at&quot;, null: false<br>end</pre><p>No more id: false with verbose column definitions.</p><p><strong>Model Extensions for Auto-Generation<br></strong>Need to generate UUIDs/ULIDs for non-primary-key columns? Sure you can!</p><pre>class User &lt; ApplicationRecord<br>  generates_uuid :api_token<br>  generates_ulid :tracking_id, unique: true<br>end</pre><pre>user = User.create!(email: &quot;dev@example.com&quot;)<br>user.api_token    #=&gt; &quot;550e8400-e29b-41d4-a716-446655440000&quot;<br>user.tracking_id  #=&gt; &quot;01ARZ3NDEKTSV4RRFFQ69G5FAV&quot;</pre><p>If you’re curious I prepared a spec especially for checking each of the ID types performance. Just run benchmarks on your own hardware:</p><pre>bundle exec rspec --tag performance</pre><h3>What I Learned Building This</h3><pre>ActiveRecord::Type.register(:uuid, SqliteCrypto::Type::Uuid, adapter: :sqlite3)</pre><p><strong>1. Rails’ type system is more extensible than I expected<br></strong>Registering custom types is straightforward:</p><p>The hard part was getting the schema dumper to output clean id: :uuid instead of verbose column definitions. That required prepending modules at exactly the right point in Rails&#39; initialization sequence.</p><h3>2. Test against real Rails versions, not just your development version</h3><p>My CI matrix tests against Ruby 3.1–3.4 and Rails 7.1–8.1. I found edge cases that only appeared in specific combinations-Rails 8.0’s schema dumper behaved differently than 7.2’s in subtle ways.</p><h3>Try It</h3><pre># Gemfile<br>gem &quot;sqlite_crypto&quot;</pre><p>If you hit issues, <a href="https://github.com/bart-oz/sqlite_crypto/issues">open a GitHub issue</a>. If it helps your project, consider starring the repo-it helps others discover the gem.</p><p><strong>Links:</strong></p><ul><li><a href="https://github.com/bart-oz/sqlite_crypto">GitHub Repository</a></li><li><a href="https://rubygems.org/gems/sqlite_crypto">RubyGems</a></li><li><a href="https://github.com/bart-oz/sqlite_crypto/blob/main/CHANGELOG.md">Changelog</a></li></ul><h3>One More Thing</h3><p>If you see gaps that you hit in your Rails + SQLite workflow, feel free to share it with me. I’m genuinely curious what other pain points exist in this new SQLite-first world.</p><p><em>Building something with sqlite_crypto? I’d love to hear about it. Drop a comment or find me on GitHub.</em></p><p><em>Originally published at </em><a href="https://dev.to/bart-oz/uuids-in-rails-sqlite-shouldnt-be-this-hard-so-i-built-a-gem-210c"><em>https://dev.to</em></a><em> on December 22, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63f56a4a3bd9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Volvo Threads a Fine Line]]></title>
            <link>https://medium.com/@bart_oz/volvo-threads-a-fine-line-2bc78907f60b?source=rss-baceef3e1737------2</link>
            <guid isPermaLink="false">https://medium.com/p/2bc78907f60b</guid>
            <category><![CDATA[advertisement]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <category><![CDATA[video-marketing]]></category>
            <category><![CDATA[advertising]]></category>
            <category><![CDATA[online-marketing]]></category>
            <dc:creator><![CDATA[Bart Ozdoba]]></dc:creator>
            <pubDate>Wed, 02 Nov 2016 08:07:36 GMT</pubDate>
            <atom:updated>2016-11-02T08:07:36.429Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FKnGcBstqxwc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DKnGcBstqxwc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FKnGcBstqxwc%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4479eca4462becba0fdc71541751fbb5/href">https://medium.com/media/4479eca4462becba0fdc71541751fbb5/href</a></iframe><h3>Volvo Threads a Fine Line</h3><p>I was not the only one recently affected by the Halloween mood. The last production of the well known <a href="https://twitter.com/volvocarsglobal">@VolvoCarsGlobal</a> brand cleverly answered the question how to stay alive on All Saints’ Day and not fall victim to the advertising depression.</p><p>The most recent advertisement by Volvo promotes the brand in an especially interesting and quite controversial way. “Irony of life” — that’s how I would define the deaths of the characters from the advertisement, who one by one vanish from the face of the earth. Volvo presents only a few circumstances with which one can cease to exist:</p><ul><li>By being hit by a bus</li><li>Being pecked to death by a swarm of pigeons</li><li>Accidentally digging up an old bomb in the garden</li><li>Being crushed by a cabinet in the saloon</li><li>Suicide by hanging</li><li>Or by a heart attack</li></ul><p>The brand producing luxurious cars attempts to save us from… a question arises, from what? Perhaps the creators meant the simple human thoughtlessness which in a painful way touched the characters? In such a situation the brand acts as a hero, improving our sense of security. I convinced that it was precisely about that, up to the point where the frame with the hanging figures appeared. That is when my logic was broken, and I began to search for other traces to understand what Volvo tries to tell me.</p><p>So, I anxiously awaited what would happen next. The final, climactic scene features an old man speeding in the newest Volvo. The old man, excited about the ride, falls victim to a heart attack — at least that is what his behavior seems to indicate. At the same time, a random man resembling Dr. Watson (only without the glasses) on a walk with his three doggy friends, appears on the street.</p><p>The strand of bad luck ends with just one death, in this case, namely the old man dying inside of his beautiful V. So, the creators of the advertisement decided to show their flagship vehicle in a situation in which the driver dies inside the car. Dr. Watson came out alive and his dogs did not even twitch a muscle gazing into the hood of the car. They were either admiring the beauty of the construction or the fact that they were not smeared all over the road.</p><blockquote><strong>V is for Volvo who knows how to cheat</strong><em> — this sentence appears at the end of the advertisement, and it immediately got my curiosity. A few answers to the question what the author had in mind, were born in my head:</em></blockquote><ul><li>Slyness in saving the pedestrians from inane death?</li><li>Prolonging our human infirmity through the Volvo brand?</li><li>Ensuring a peaceful death for all Volvo drivers?</li></ul><p>I’m curious what do you think dear readers. What did the authors of the advertisement have in mind?</p><p><em>Originally published at </em><a href="http://digitaily.com/volvo-threads-a-fine-line/"><em>digitaily.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2bc78907f60b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Content Mantra]]></title>
            <link>https://medium.com/@bart_oz/content-mantra-a587eb0c1183?source=rss-baceef3e1737------2</link>
            <guid isPermaLink="false">https://medium.com/p/a587eb0c1183</guid>
            <category><![CDATA[content-marketing]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[online-marketing]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <dc:creator><![CDATA[Bart Ozdoba]]></dc:creator>
            <pubDate>Wed, 02 Nov 2016 08:00:24 GMT</pubDate>
            <atom:updated>2016-11-02T08:00:24.931Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*bzBjP2Tynmp5N8abjTR7BQ.jpeg" /></figure><p><strong>Asking what was first, the chicken or the egg makes absolutely no difference in this case because it’s obvious it was… content.</strong></p><p><strong>The power of the word</strong><br> It was used since the dawn of the universe with a colossal force which nothing can defy. Can we say that today content rules the world? On the Internet, absolutely yes! Those who are able to take advantage of the potential lying in words and create something unique from them are the ones who succeed.</p><p>I don’t reinvent the wheel by writing that we are all curious by nature, we want to know, and if possible, everything at once. If we don’t know something, we immediately begin to search for the answers to the questions which baffle us.</p><p>I’m also not setting my foot on the Moon by saying that acting as influencers or brands communicating with users, what is primarily needed to be learned is the method and what the users are looking for, in order to provide the right answer in the right place.</p><p><strong>Dig, and do dig deep</strong><br> Sometimes I think that content marketing is like digging a well. First of all, one has to think quite a lot about the right place to dig. Next, there is the hard work which will pay off in the future for those who had a hunch. Success? If the life-giving water flows from our source, then we are going to be able to provide for the many thirsty people.</p><p>Such a source are, without a doubt, the readable media (my favorite) such as <a href="https://twitter.com/Entrepreneur">@Entrepreneur</a>, <a href="https://twitter.com/Marketing_Mag">@Marketing_Mag</a> <a href="https://twitter.com/CMIContent">@CMIContent</a>, but also influencers like <a href="https://twitter.com/jeffbullas">@JeffBullas</a>, <a href="https://twitter.com/Robert_Rose">@Robert_Rose</a>, <a href="https://twitter.com/sujanpatel">@SujanPatel</a> <a href="https://twitter.com/randfish">@RandFishkin</a>.</p><p>There is nothing more to add, just to take blades in hands; I mean keyboards.</p><p>With this short post, I hereby open my new blog.</p><p><em>Originally published at </em><a href="http://digitaily.com/content-mantra/"><em>digitaily.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a587eb0c1183" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Steps to Efficient PUSH Message Marketing]]></title>
            <link>https://medium.com/@bart_oz/3-steps-to-efficient-push-message-marketing-c61094a702?source=rss-baceef3e1737------2</link>
            <guid isPermaLink="false">https://medium.com/p/c61094a702</guid>
            <category><![CDATA[digital-marketing]]></category>
            <category><![CDATA[push-notification]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[push-message-marketing]]></category>
            <dc:creator><![CDATA[Bart Ozdoba]]></dc:creator>
            <pubDate>Fri, 19 Aug 2016 14:52:31 GMT</pubDate>
            <atom:updated>2016-08-22T14:15:41.408Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*RQpP1aLTF1rJmKQaIWIgkw.jpeg" /></figure><p>How often do you send PUSH notifications and not become annoying and cause subscribers to block their consent on a mass scale? Here are 3 ways to prevent that from happening.</p><p><strong>1. PUSH equals quality content</strong><br> Send PUSH notifications only when you actually have something of importance to convey to your subscribers. A promotion, discount, time-limited sales or introduction of a new product to your store are an excellent opportunity to send out a PUSH.</p><p>Try not to create a promotional overkill, as this may in fact discourage a large number of your subscribers, who would like to learn not only about sales, but also what’s new on the blog, or how was the event that your company attended.</p><p><strong>2. Link to the source article</strong><br> Remember, if you want to inform your subscribers about a new attractive product, make sure you put a direct link into the PUSH notification. The message contents should also be in tune with what they’ll find after following the link. No one likes to be misinformed or misguided. Avoid clickbait at all cost!</p><p>Strive to provide your subscribers with content that goes beyond your website. You can also use PUSH notifications to invite people to join your Facebook event or follow your Twitter account.</p><p><strong>3. Content is king</strong><br> Follow this rule to develop catchy content intended for PUSH notifications. You’ll see way better CTRs if you’ll say something like: <em>Miracles do happen! Up to 90% off for the entire collection</em>, or <em>New models have arrived. The shelves can barely hold them.</em></p><p>Writing short pieces of content isn’t easy. Especially, when users receive around 20 messages per minute from various sources. Stand out or perish — here’s another rule to follow if you’re a content marketer these days.</p><p><em>Originally published at </em><a href="https://pushango.com/3-steps-efficient-push-message-marketing/"><em>pushango.com</em></a><em> on August 19, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c61094a702" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you draw attention with a single sentence?]]></title>
            <link>https://medium.com/@bart_oz/how-do-you-draw-attention-with-a-single-sentence-99a73810bce1?source=rss-baceef3e1737------2</link>
            <guid isPermaLink="false">https://medium.com/p/99a73810bce1</guid>
            <category><![CDATA[push-notification]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[pushango]]></category>
            <category><![CDATA[push-message-marketing]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <dc:creator><![CDATA[Bart Ozdoba]]></dc:creator>
            <pubDate>Thu, 16 Jun 2016 05:37:52 GMT</pubDate>
            <atom:updated>2016-06-16T05:38:47.057Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*DXdZfHAiNO08PPG_uNJadg.jpeg" /></figure><p><strong>“We’re more anxious to speak than to be heard”, said Henry David Thoreau. How do you make your marketing pitches hit the nail on the head and be remembered instead of sounding like empty slogans, or otherwise leave their mark on the audience?</strong></p><p><strong>Fly, fast, fitting!</strong></p><p>It’s easy to elaborate to the point of exhausting the topic, however, the question is, whether every bit of what you were trying to say was necessary and worthy of all the attention? Sometimes, a single, well-crafted sentence is all it takes to grab the subscriber’s attention. The skill of writing short and efficient sentences will come in handy when developing the contents of PUSH notifications.</p><p><strong>Every space counts</strong> <br>When creating a PUSH notification in our app, you’ll have 30 characters for the headline and 40 characters for line two.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*JNfj5yZWDPbAvz0L.jpg" /></figure><p><strong>Now, here are 5 tips that will help you develop engaging PUSH notifications:</strong></p><p>1. Draw the recipient’s attention using a stand-out expression or phrase.</p><p>2. Use light writing style, avoid unnecessary jargon. This is supposed to be nice and easy, like Snapchat!</p><p>3. Try not to use any special characters, as the message may become incomprehensible.</p><p>4. Get inspired by everyday life. Imagine situations and what people are up to — by sending PUSH notifications you’re putting them a little bit off the track. Make sure you have something cool and important to tell them.</p><p>5. Make the URL in the message the extension of its contents. The recipient needs to be able to learn more about what’s being said in the PUSH notification.</p><p><strong>Good luck!</strong></p><p><em>Originally published at </em><a href="https://pushango.com/blog/how-do-you-draw-attention-with-a-single-sentence.html"><em>pushango.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99a73810bce1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>