<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>App Development &#8211; Hodfords Blog</title>
	<atom:link href="https://www.hodfords.com/blog/category/app-development/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.hodfords.com/blog</link>
	<description>This is the Official Blog for Hodfords.</description>
	<lastBuildDate>Fri, 07 Oct 2022 08:55:18 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.3.18</generator>
	<item>
		<title>The importance of user research</title>
		<link>https://www.hodfords.com/blog/the-importance-of-user-research/</link>
				<comments>https://www.hodfords.com/blog/the-importance-of-user-research/#respond</comments>
				<pubDate>Fri, 07 Oct 2022 08:55:15 +0000</pubDate>
		<dc:creator><![CDATA[Hodfords]]></dc:creator>
				<category><![CDATA[App Development]]></category>
		<category><![CDATA[Methodology]]></category>

		<guid isPermaLink="false">http://www.hodfords.com/blog/?p=1881</guid>
				<description><![CDATA[User research is the process of understanding user behaviours needs and motivations through observation techniques, task analysis and other feedback methodologies. This is a crucial process within the design phase. The complexity&#8230;]]></description>
								<content:encoded><![CDATA[
<p>User research is the process of understanding user behaviours needs and motivations through observation techniques, task analysis and other feedback methodologies. This is a crucial process within the design phase. The complexity of UI/UX between products requires serious thought, partly because it involves thinking of what users require, beyond what has been asked for.</p>



<h2>But why is it so important</h2>



<h3>It facilitates the design of better
products.</h3>



<p>Without this process in the design phase, products can miss the mark in identifying and treating pain points users might have when engaging with the product and may not address user needs in an effective and meaningful manner. Either outcome can lead to a reduction in user engagement. Increased understanding of how users behave therefore bridges the gap in uncertainty that companies have on their target user base.</p>



<h3>It saves time, resources, and
capital. </h3>



<p>Though this process can seem daunting and time-consuming, the risks that are associated with creating a product that is erroneous for users are worth the prior research. Finding out insights about the users’ needs rather than guessing, will mean saving unnecessary time after product launch, and fixing bugs and usability issues. It is therefore worth putting in the research time beforehand to mitigate this risk.</p>



<h3>Business Failure.</h3>



<p>Having not identified what users need prior to launching can lead users to not engage with the product. A lack of faith in the product initially may lead to target users switching to alternative products. This may lead to product failure and if your business is tied entirely to this one product, can sink the business.</p>



<p>User research is therefore the
facilitator of success for software products and must be acknowledged.</p>
]]></content:encoded>
							<wfw:commentRss>https://www.hodfords.com/blog/the-importance-of-user-research/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
							</item>
		<item>
		<title>Non-Native and Native App Development, a Comparison.</title>
		<link>https://www.hodfords.com/blog/non-native-native-app-development-a-comparison/</link>
				<comments>https://www.hodfords.com/blog/non-native-native-app-development-a-comparison/#respond</comments>
				<pubDate>Fri, 30 Sep 2022 04:10:40 +0000</pubDate>
		<dc:creator><![CDATA[Hodfords]]></dc:creator>
				<category><![CDATA[App Development]]></category>
		<category><![CDATA[UI and Mobile]]></category>

		<guid isPermaLink="false">http://www.hodfords.com/blog/?p=1818</guid>
				<description><![CDATA[The terms non-native and native apps are commonplace in the software industry. But what do they mean to those who are unfamiliar with software development and may want to develop an app&#8230;]]></description>
								<content:encoded><![CDATA[
<p>The terms non-native and native apps are commonplace in the software industry. But what do they mean to those who are unfamiliar with software development and may want to develop an app someday… probably not a whole lot.&nbsp;</p>



<p>Let’s briefly define these terms, to better understand them. </p>



<h3>Native App Development</h3>



<p>Native apps are downloadable mobile applications that are tailored and specific to operating systems such as iOS or Android. These apps are indigenous to the device it was developed for.</p>



<h3>Non-Native App Development&nbsp;</h3>



<p>Non-native apps- otherwise known as web apps- are designed to run on multiple platforms, instead running off web browsers rather than a specific operating system. These are built with mobile experience put first, which also facilitates desktops.</p>



<p>So, one utilises a web browser- to cover multiple platforms, whilst the other utilises a specific operating system- to target a specific operating system. What positives, and drawbacks of using these different approaches to app development?</p>



<h3><strong>Native Advantages</strong></h3>



<p>The first key benefit to developing native
apps is the increased usability of the app. Due to the app being developed to
serve a specific operating system (i.e., iPhone’s iOS system), the apps are
optimized to run and serve the specific device. A greater user experience (UX)
is produced as these apps can take advantage of functions within specific
operating systems. The greater the UX, the more likely that app users will use
and stay on the application.</p>



<p>Another key benefit of native apps is the efficiency. Having an app built for a particular platform and stored in the device allows it to make use of the processing power. Also, the native apps’ software capabilities for utilising its devices’ hardware are stored, providing responsive load times to app commands.</p>



<h3><strong>Native Disadvantages</strong></h3>



<p>One of the biggest drawbacks to Native app development is the cost. If looking to serve multiple operating systems whilst maintaining the efficiency and utility that native apps provide, this now becomes significantly more expensive and time-consuming. Separate code bases and developers are required to create two different versions of the app that runs on differing platforms.</p>



<p>Another disadvantage is the ongoing updates that are necessary to keep the app working and efficient. Native apps are constantly updating due to:</p>



<ul><li>The ongoing technological developments that occur in devices, so ensuring the apps are consistently optimised with the most updated versions of the OS. </li><li>Malfunctions and bug repairs are common in native apps, so maintenance is ongoing.</li></ul>



<h3>Non-Native Advantages</h3>



<p>One of the biggest advantages that come of non-native app development is its multiplatform service. These web applications are easily accessible and are a much cheaper option compared to designing different native apps for different operating systems. This reduces the time and money spent on development.</p>



<h3>Non-Native Disadvantages&nbsp;</h3>



<p>The big disadvantage to non-native app development is that it comes with reduced user experience, compared to native apps. Though non-native apps can run on multiple platforms, their broadness means it doesn’t fully utilise different operating systems&#8217; capabilities. This is a detriment to the UX and therefore could affect user engagement.</p>



<h3><strong>So, Which is Better?</strong></h3>



<p>Native apps provide superior capabilities for utilising device components. It is therefore always advised to go for this option if you have the capital and resources to fund the development of a native app. If resources and capital is low, a non-native app may be appropriate. <strong> </strong></p>
]]></content:encoded>
							<wfw:commentRss>https://www.hodfords.com/blog/non-native-native-app-development-a-comparison/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
							</item>
	</channel>
</rss>
