<?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 Bhavika Patel on Medium]]></title>
        <description><![CDATA[Stories by Bhavika Patel on Medium]]></description>
        <link>https://medium.com/@bhavikaap711?source=rss-f20c660bd749------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8Ya88unM9OBt2MIyMfklYg.jpeg</url>
            <title>Stories by Bhavika Patel on Medium</title>
            <link>https://medium.com/@bhavikaap711?source=rss-f20c660bd749------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:31:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bhavikaap711/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[Native or Hybrid mobile app development ?]]></title>
            <link>https://medium.com/graymatrix/native-or-hybrid-mobile-app-development-faa13dd224bd?source=rss-f20c660bd749------2</link>
            <guid isPermaLink="false">https://medium.com/p/faa13dd224bd</guid>
            <category><![CDATA[native-app-vs-hybrid-app]]></category>
            <category><![CDATA[native-app-development]]></category>
            <category><![CDATA[hybrid-app-development]]></category>
            <dc:creator><![CDATA[Bhavika Patel]]></dc:creator>
            <pubDate>Fri, 04 Dec 2020 05:44:06 GMT</pubDate>
            <atom:updated>2020-12-04T05:48:55.752Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Native or Hybrid mobile app development ?</strong></h3><figure><img alt="Native or Hybrid mobile app development ?" src="https://cdn-images-1.medium.com/max/1024/0*OuP6sLDifC13LCSa" /></figure><p>The Internet is flooded with debates about which approach to adopt when it comes to mobile app development. There are two types of mobile application development one can investigate for versatile mobile app development ventures: native and hybrid. Let’s try to know each type to make our decision about the best method for app development.</p><h3><strong>Native App</strong></h3><p>Native mobile apps are the most common type of app. It is a software application built in a specific programming language, for the specific device platform, either iOS or Android. iOS apps are developed using Swift or Objective-C and Android apps are built in Java language. A native app is developed specifically for one platform. It can be installed through an application store such as Google Play Store or Apple’s App Store.</p><h3><strong>Hybrid App</strong></h3><p>A hybrid app is essentially a combination of a native app and a web app. The application borrows cross-compatible web technologies, such as HTML5, CSS and Javascript and utilizes a portion of native code for greater adaptability to the user device. It is given a thin native shell with WebView to access the native app system functionality.</p><p><strong>DEVELOPMENT COST<br></strong>Native app development on the requires the writing of a completely different app for each platform. Different skill sets required to develop and maintain the same application on each platform which adds to the cost.</p><p>Hybrid app development has a single code base for all platforms means writing once and running on all platforms. As development efforts are half the cost is lower for hybrid.</p><p><strong>CODEBASE<br></strong>When it comes to native app, iOS apps will not run on Android and vice versa, so you will have to work with different codebases for every platform you choose to build in.</p><p>Most hybrid tools will enable portability of a single codebase to the major mobile platforms.</p><p><strong>DEVICE ACCESS<br></strong>Native app : Platform SDK enables access to aIl device APIs</p><p>Hybrid app : Many devices API closed to web apps can be accessed, depending on the tool.</p><p><strong>Ul &amp; DESIGN CONSISTENCY<br></strong>With native app, the platform comes with familiar, original Ul components. Richly appealing user interface design.</p><p>For hybrid app, UI frameworks can achieve a better native look. Quality is a mix between native and HTML5 visual appeal, but not as rich as native.</p><p><strong>DISTRIBUTION<br></strong>App store provides marketing beneﬁts but also have requirements and restriction</p><p>App store provides marketing beneﬁts but also have requirements and restriction</p><p><strong>PERFORMANCE<br></strong>Native code has direct access to platform functionality, resulting in the fastest, most reliable and most responsive experience to users.</p><p>With hybrid code for complex apps, the abstraction layers often prevent native-like performances.</p><p><strong>USER EXPERIENCE<br></strong>With native apps you can seamlessly tap into the wider functionality of a mobile device, leveraging the camera, microphone, GPS, swipe gestures, and more.</p><p>Because of its content being based on web technology, hybrid apps can be slower to load than native apps.</p><p><strong>Summary <br></strong>The fight between hybrid applications and native applications is never going to end in light of the fact that, truly, there’s a spot for both.</p><p>The choice to pick hybrid or native depends on objectives and the needs of the organisation mainly :</p><ul><li>What are you trying to accomplish with your app?</li><li>When do you need it?</li><li>Which skills do you have in-house?</li><li>How much can you spend on the app?</li><li>What features do you require?</li><li>How many platforms do you want to reach?</li></ul><p>Decision to finalise will be dictated by your resources and the needs of your end-user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=faa13dd224bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/graymatrix/native-or-hybrid-mobile-app-development-faa13dd224bd">Native or Hybrid mobile app development ?</a> was originally published in <a href="https://medium.com/graymatrix">Gray Matrix</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best Design/HTMLCSS practice for emailers that are compatible for maximum email clients]]></title>
            <link>https://medium.com/graymatrix/best-design-htmlcss-practice-for-emailers-that-are-compatible-for-maximum-email-clients-d7e104cb0153?source=rss-f20c660bd749------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7e104cb0153</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[emailers]]></category>
            <category><![CDATA[formatting]]></category>
            <dc:creator><![CDATA[Bhavika Patel]]></dc:creator>
            <pubDate>Thu, 03 Dec 2020 11:38:05 GMT</pubDate>
            <atom:updated>2020-12-04T07:09:33.574Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Best Design/HTML CSS practice for emailers that are compatible for maximum email clients</strong></h3><figure><img alt="Best Design/HTMLCSS practice for emailers that are compatible for maximum email clients" src="https://cdn-images-1.medium.com/max/1024/0*VdYSwz5wLc_smRW0" /></figure><p><strong>Ideal width :</strong> The ideal email width is 600px wide to render properly on all devices and browsers.</p><p><strong>Handheld first :</strong> Approx 65% of emails are now opened on mobile devices. This means that you can no longer ignore the idea of designing for mobile devices.</p><p><strong>Use entity code for special characters :</strong> On the off chance that your email service provider utilizes an alternate sort of encoding from the thoughtful you chose for your email, it might cause your exceptional characters (like ©) to show up inaccurately, regularly as a square or junk characters. This can influence quotes and punctuations, too. To maintain a strategic distance from this issue, utilize a character entity code.</p><p><strong>Minimal images :</strong> On the off chance that a subscriber has turned off images, your entire email might be lost. In the event that you should utilize styled alt text to ensure your message gets across if the picture doesn’t load. Use a combination of colors &amp; fonts to design your emailer, use images only for important and unavoidable components. Keep images crisp but optimize for load time with a resolution of 72 dpi.</p><p><strong>Email-safe fonts : </strong>Every inbox will render fonts differently, hence use the Email-safe Fonts, these fonts come preloaded on most computers and render consistently over 90% of the time. At minimum, use 13 or 14 pixels for the text and 20–22 for the titles. This will make your email much more readable on a medium to small screen. Some of the email-safe fonts :</p><ul><li>Arial</li><li>Arial Black</li><li>Comic Sans MS</li><li>Courier New</li><li>Georgia</li><li>Impact</li><li>Times New Roman</li><li>Trebuchet MS</li><li>Verdana</li></ul><p><strong>Use Old School HTML coding method</strong>: The most important guideline for HTML emails is that CSS layout just doesn’t work. The major email clients either offer no support at all, or mess up in frustratingly different ways. Tables are the most reliable way to achieve a consistent layout. They also allow you to replicate something that many email clients otherwise don’t allow. With tables, you can take advantage of the align attribute, which was the predecessor of modern CSS floats. There are some problems using tables, too, as learned the hard way. Here are a few tips for dealing with tables in an email.</p><p>Create a structure that is flexible enough. The main table should be divided into 3 sections, mainly header, content and footer. Each section should have its own table to design further this way; differences in structure of either of the components will not impact others.</p><p>Use properties of HTML tags to apply theme/design to the content, using this native code helps email to be compatible on most of the email clients, especially Outlook which renders html with Microsoft Word: the word processor in all it’s Windows Desktop apps.</p><p>Set widths in every cell instead of on the table :</p><p>&lt;table cellspacing=”0&quot; cellpadding=”0&quot; border=”0&quot;&gt; <br>&lt;tr&gt; <br>&lt;td width=”310&quot;&gt;&lt;/td&gt; <br>&lt;td width=”290&quot;&gt;&lt;/td&gt; <br>&lt;/tr&gt; <br>&lt;/table&gt;</p><p>Most of the email clients render HTML differently when it comes to width td cells, so it’s better to us pixel units for width as it is most reliable.</p><p>Use nested tables for all three sections as explained above (a), this will help for consistency and better formatting. It’s old school, but it’s tried-and-true.</p><p>Avoid using advanced css, use as much as possible HTML tag properties, eg if you want to give color to background inside a section which in laid in the Table, use bgcolor=”#000”. Use inline css wherever applicable, some of the email clients remove/ignore &lt;style&gt; tags.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7e104cb0153" width="1" height="1" alt=""><hr><p><a href="https://medium.com/graymatrix/best-design-htmlcss-practice-for-emailers-that-are-compatible-for-maximum-email-clients-d7e104cb0153">Best Design/HTMLCSS practice for emailers that are compatible for maximum email clients</a> was originally published in <a href="https://medium.com/graymatrix">Gray Matrix</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Generating printable PDF files from HTML/CSS page]]></title>
            <link>https://medium.com/graymatrix/generating-printable-pdf-files-from-html-css-page-ec31c47802db?source=rss-f20c660bd749------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec31c47802db</guid>
            <category><![CDATA[cssforpdf]]></category>
            <category><![CDATA[print-pdf]]></category>
            <category><![CDATA[htmlforpdf]]></category>
            <dc:creator><![CDATA[Bhavika Patel]]></dc:creator>
            <pubDate>Fri, 27 Nov 2020 08:57:17 GMT</pubDate>
            <atom:updated>2020-11-27T11:43:05.552Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aYwpNLyTPy_6t3R3" /></figure><p>In this digital world there are days when some of your applications/forms/content are to be printed. This is where you have to develop HTML that is rendered to create PDF.</p><p>Offlate our team had worked on lot of forms/tickets/receipts that were digitized for records and printed for reference where there were different set of challenges we faced and following are few tips to get it right in shortest time, although a lot depend on type of content being rendered.</p><p>Basics of HTML for printing a file that will work in almost all the prints :-</p><ul><li>go native, use as much as you can the old school HTML tags like &lt;table&gt; &lt;p&gt; &lt;ul&gt; &lt;li&gt; etc</li><li>use properties of HTML tags like width, cellpadding, cellspacing, align, etc</li><li>use formatting tags like &lt;u&gt; &lt;b&gt; etc</li><li>avoid inline css</li><li>avoid advance / css 3 properties</li></ul><p>Few essential css to consider :-</p><p><strong>THE @PAGE RULE</strong></p><p>The @page rule is to specify aspects of a page box.</p><p>@page {</p><p>size: 5.5in 8.5in;</p><p>}</p><p>or</p><p>@page {</p><p>size: A4;</p><p>}</p><p>or</p><p>@page {</p><p>size: A4 landscape;</p><p>}</p><p>Selectors to define different margin sizes for our pages.</p><p>@page :left {</p><p>margin-left: 3cm;</p><p>}</p><p>@page :right {</p><p>margin-left: 4cm;</p><p>}</p><p>@page :first {</p><p>}</p><p>The :blank pseudo-class selector targets any page that is “intentionally left blank.” To add this text, we can use generated content that targets the top-center margin box.</p><p>@page :blank {</p><p>@top-center { content: “This page is intentionally left blank.” }</p><p>}</p><p><strong>PAGE BREAKS</strong></p><p>h1</p><p>{</p><p>page-break-before: always;</p><p>}</p><p>To avoid breaks directly after a heading, use page-break-after.</p><p>h1, h2, h3, h4, h5</p><p>{</p><p>page-break-after: avoid;</p><p>}</p><p>To avoid breaking figures and tables, use the page-break-inside property.</p><p>table, figure</p><p>{</p><p>page-break-inside: avoid;</p><p>}</p><p><strong>COUNTERS</strong></p><p>CSS counters let you adjust the appearance of content based on its location in a document. To use a CSS counter, it must first be initialized to a value with the counter-reset property (0 by default). The value of a counter can be displayed using either the counter() or counters() function in a content property as shown below :</p><p>@page { counter-increment: page }</p><p>This rule instructs the layout engine to create a counter called “page” it can be anything). This counter is incremented for each page. As with any counter, you can then use the current value of the counter anywhere in the document</p><p>For example:</p><p>CSS -&gt; #pageNumber { content: counter(page) }</p><p>HTML -&gt; &lt;span id=”pageNumber”&gt;&lt;/span&gt;</p><p>For example with this CSS rule:</p><p>#pageNumber { content: counter(page) }</p><p>and this piece of HTML:</p><p>&lt;span id=”pageNumber”&gt;&lt;/span&gt;</p><p>You can use the current page number counter as content in the HTML document. You can even go further. Say you want to start your page number at 10. You can then use the @page:first rule to reset the counter for the first page to value 9.</p><p>@page { counter-increment: page } @page:first { counter-reset: page 9 }</p><p>The combination of both rules will reset the counter for the first page to 9. Then for each page (including the first) it will increment the counter. This results in a counter value of 10 for the first page, 11 for the second and so on.</p><p><strong>INCLUDING WEB FONTS</strong></p><p>@import url(https://medium.com/%E2%80%98%3Ca%20href=%22/service/https://fonts.googleapis.com/css?family=Montserrat:300,300i,400,500,700i%27%22%3Ehttps://fonts.googleapis.com/css?family=Montserrat:300,300i,400,500,700i&#39;%3C/a%3E);</p><p>.heading {</p><p>font-family: Montserrat, Serif;</p><p>font-weight:500;</p><p>}</p><p>Use @import rule to web font into the pdf.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec31c47802db" width="1" height="1" alt=""><hr><p><a href="https://medium.com/graymatrix/generating-printable-pdf-files-from-html-css-page-ec31c47802db">Generating printable PDF files from HTML/CSS page</a> was originally published in <a href="https://medium.com/graymatrix">Gray Matrix</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>