<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Timothy Broome</title>
    <description>The latest articles on DEV Community by Timothy Broome (@timbroome).</description>
    <link>https://dev.to/timbroome</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1808522%2Fe2623151-d23b-449e-9dbc-372fe970fdb5.png</url>
      <title>DEV Community: Timothy Broome</title>
      <link>https://dev.to/timbroome</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/timbroome"/>
    <language>en</language>
    <item>
      <title>First Vertical - log a time period against a user - iPhone app to Supabase - WIP</title>
      <dc:creator>Timothy Broome</dc:creator>
      <pubDate>Fri, 19 Jul 2024 23:32:40 +0000</pubDate>
      <link>https://dev.to/timbroome/first-vertical-log-a-time-period-against-a-user-iphone-app-to-superbase-wip-1g2p</link>
      <guid>https://dev.to/timbroome/first-vertical-log-a-time-period-against-a-user-iphone-app-to-superbase-wip-1g2p</guid>
      <description>&lt;p&gt;It could be a contentious view; but before every view and pixel are designed I like to establish some real tangible functionality first. I find it really helps the design process to have usable functionality in your hand that you can interact with and consider. &lt;/p&gt;

&lt;p&gt;I don't advise spending a lot of time on this initial scaffolding version; produce the minimum that provides some kind of useful functionality.&lt;/p&gt;

&lt;p&gt;Ultimately and pragmatically it's better to finish some primitive but useful screens, then a design masterpiece that's never implemented. In a real-world project continuous delivery gives assurance and peace of mind to stakeholders.&lt;/p&gt;

&lt;h4&gt;
  
  
  Create Universal Swift Ui App
&lt;/h4&gt;

&lt;h4&gt;
  
  
  Create Supabase Project and setup the iOS Supabase client
&lt;/h4&gt;

&lt;h4&gt;
  
  
  Scaffold initial screens and basic navigation
&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;Login&lt;/li&gt;
&lt;li&gt;Log time&lt;/li&gt;
&lt;li&gt;Time list&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  Setup basic log-in, log-out screens
&lt;/h4&gt;

&lt;h4&gt;
  
  
  Create time-log screen
&lt;/h4&gt;

&lt;h4&gt;
  
  
  Create time-list screen
&lt;/h4&gt;




&lt;h3&gt;
  
  
  Useful resources
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://docs.swift.org/swift-book/documentation/the-swift-programming-language/" rel="noopener noreferrer"&gt;Swift Programming Language Reference&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://youtu.be/enVDRqzmudo" rel="noopener noreferrer"&gt;Supabase - Swift Database &amp;amp; Auth&lt;/a&gt;&lt;/p&gt;

</description>
      <category>supabase</category>
      <category>ios</category>
      <category>swiftui</category>
    </item>
    <item>
      <title>Tech choices and why - WIP</title>
      <dc:creator>Timothy Broome</dc:creator>
      <pubDate>Fri, 19 Jul 2024 23:27:34 +0000</pubDate>
      <link>https://dev.to/timbroome/tech-choices-and-why-wip-1h78</link>
      <guid>https://dev.to/timbroome/tech-choices-and-why-wip-1h78</guid>
      <description></description>
    </item>
    <item>
      <title>High-level vision, vision board and requirements - WIP</title>
      <dc:creator>Timothy Broome</dc:creator>
      <pubDate>Fri, 19 Jul 2024 23:22:55 +0000</pubDate>
      <link>https://dev.to/timbroome/high-level-vision-vision-board-and-requirements-wip-5k9</link>
      <guid>https://dev.to/timbroome/high-level-vision-vision-board-and-requirements-wip-5k9</guid>
      <description>&lt;h2&gt;
  
  
  High Level Vision
&lt;/h2&gt;

&lt;p&gt;As described in my intro-post; I want to create an app that allows me to &lt;strong&gt;log productive time&lt;/strong&gt; and then allow the &lt;strong&gt;exploration of cross-sections of that data&lt;/strong&gt;. Data should be &lt;strong&gt;visualised&lt;/strong&gt; in a mixture of &lt;strong&gt;numerical totals&lt;/strong&gt; as well as &lt;strong&gt;graphics&lt;/strong&gt; to efficiently provide a range of perspectives in one view.&lt;/p&gt;

&lt;p&gt;Important metrics are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;productive time&lt;/li&gt;
&lt;li&gt;planning time&lt;/li&gt;
&lt;li&gt;tasks attempted (started)&lt;/li&gt;
&lt;li&gt;tasks completed&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Useful additional context:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Task size&lt;/li&gt;
&lt;li&gt;Task complexity&lt;/li&gt;
&lt;li&gt;Task readiness (can be executed) &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To achieve this a level of task-management will be needed to log time against tasks. However the ui should me nimble and easy to navigate. I do not want to re-create Jira or monday.com. A task should be quick to add and have the minimal information. Additional resources should be provided through links; for example; a work Jira task, an image, a website etc.&lt;/p&gt;

&lt;h2&gt;
  
  
  Vision Board
&lt;/h2&gt;

&lt;p&gt;When designing and to communicate a vision to others; I find it helpful to create a vision/mood-board of related UIs/apps/experiences etc. These can be labeled to add flavour&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Enticing data visualisation views from Strava and Smashrun. This new app should attempt to re-create this experience but for productivity&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F5xxb93r5eraz4gm6th7q.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F5xxb93r5eraz4gm6th7q.png" alt="Enticing data visualisation views from Strava and Smashrun. This new app should attempt to re-create this experience but for productivity" width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Requirements
&lt;/h2&gt;

&lt;p&gt;When embarking on a project it's important to formalise requirements at the start. There's often alot of excited discussion between stakeholders, designers, engineers. But its amazing how peoples minds-eyes can differ when it feels like there's a common understanding and consensus.&lt;/p&gt;

&lt;p&gt;Even as a one-man project; once embarked on all the technical details needed to build a project; the context and relative importance of requirements can be lost. Requirements are the way-points/the map to guide engineers and stakeholders through a project, and ultimately provides the finish-line to aim for..&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Strava for Productivity - weekend end-to-end project</title>
      <dc:creator>Timothy Broome</dc:creator>
      <pubDate>Fri, 19 Jul 2024 22:28:04 +0000</pubDate>
      <link>https://dev.to/timbroome/strava-for-productivity-weekend-end-to-end-project-2kk3</link>
      <guid>https://dev.to/timbroome/strava-for-productivity-weekend-end-to-end-project-2kk3</guid>
      <description>&lt;p&gt;&lt;strong&gt;Ode to running and data&lt;/strong&gt;&lt;br&gt;
Running makes me tick. I'm not a pro by any means. But with a relatively sedentary job; a dash into the fresh air gets my blood pumping; adds some good feelings to it; it also opens my mind to fresh ideas. What I enjoy as much as running itself is data. I love looking at Strava, Smashrun, Garmin Connect to study km splits, compare to previous runs on a just completed route. Look at trends, look at cumulative totals for the past week, 90 days, year. View graphs. I really enjoy this ritual. Ultimately it motivates me to keep running; to continue a trend, improve a trend, aim for a target etc.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An idea&lt;/strong&gt;&lt;br&gt;
An idea i've had for a while is; if this is so effective for running can it also be for other areas of life; i.e. productivity. If viewing some trend graphs can motivate me to getting an extra hours work done or complete some hideous admin task I keep pushing aside; i'll be all the richer for it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Self-growth goals&lt;/strong&gt;&lt;br&gt;
Although I could possibly knock this out pretty quickly as a web app; i've wanted to do something substantial in iOS. I'll try and write this blog directly as I do this; in order to document the way I work. At the very least this will be useful to me. I hope I can help others passing by too.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Steps&lt;/strong&gt;&lt;br&gt;
I'll break the process down into a number of steps; which will be sub-blog posts when completed. These will be added to whilst things evolve. Here goes!&lt;/p&gt;

</description>
      <category>howiwork</category>
      <category>buildinpublic</category>
      <category>ios</category>
      <category>design</category>
    </item>
  </channel>
</rss>
