Difference between revisions of "Tl;dr"

From Cibernética Americana
Line 20: Line 20:
  
 
Essentially it is a full design package based on the low fidelity wireframe.
 
Essentially it is a full design package based on the low fidelity wireframe.
<br><br>
+
<br><br><h1>tl;dr</h1><h4>consumer products </h4>
 +
"tl;dr[n]" is a mark signifying specific projects implemented as n below with common service delivery mechanism:
 +
<ol start="0">
 +
<li><h2> tl:dr[GT2] </h2>
 +
  <h3> A completed version of the Green Travel Carbon Footprint app with Apple, Watch and cloud service. </h3></li>
 +
<li><h2> tl:dr[TASKPM] </h2>
 +
  <h3> An iOS and Android app service for personal productivity. Version 1 simply provides a cloud based service integrating Google Calendar,  the <a href=http://taskwarrior.org>task</a> ecosys (task, timewarrior) and to MS Project. </h3></li>
 +
<li><h2> tl:dr[TLDR] </h2
 +
  <h3> (domain readiness app) a free service to tx-authenticated users of my .dom TLD that provides notifications and management of DNS and <a href=http://dnseppus.meansofproduction.biz/doc/about>EPP</a> for domain operators. </h3></li><li><h2> tl:dr[*ledger] </h2
 +
  <h3> provides same device coverage for the <a href=http://ledger-cli.org>*ledger</a> ecosys (hledger, c++ ledger, etc.) with interface to SQL Ledger (my current ERP core of choice) and Quickbooks. </h3></li>
 +
</ol>
 +
No Entrapment, No Freebies
 +
<blockquote>
 +
The dr component is useful for any domain using the standard internet systems programs and task and ledger apps similarly allow users to use their own backend services instead of my cloud services. In principle and in fact. However the distributed binaries are necessarily dependent on my biz infrastructure and offerings so you  need to have a Developer class account to get the dev kit to make them work with your backends.
 +
</blockquote>
 +
 
 +
Cloud services are available at two levels, each bundled for the whole suite. These apps are included in the sameboat personal domain service offering.
 +
<html>
 +
</html>
 
</blockquote>
 
</blockquote>

Revision as of 17:57, 9 March 2020



tl;dr ...

The software product engineering line

Software we build for consumer use, as opposed to systems software, is considered to be a part of software product engineering line with this brand name. The style is "tl" followed by colon, dash, or semicolon, followed by a square bracketed specific product name. Elements:

  • redvant implementation base.
  • wireframe approach, wireframe as production, CI concept
  • clear separation of standalone vs cloud. standalone is just on device without accessing DS.

The Look and Feel of the apps in the line

The theme, style, or graphical design concept of the look and feel package is a low fidelity wireframe mock, filled with active working content instead of crossed out static images.

Essentially it is a full design package based on the low fidelity wireframe.



tl;dr

consumer products

"tl;dr[n]" is a mark signifying specific projects implemented as n below with common service delivery mechanism:

  1. tl:dr[GT2]

    A completed version of the Green Travel Carbon Footprint app with Apple, Watch and cloud service.

  2. tl:dr[TASKPM]

    An iOS and Android app service for personal productivity. Version 1 simply provides a cloud based service integrating Google Calendar, the <a href=http://taskwarrior.org>task</a> ecosys (task, timewarrior) and to MS Project.

  3. tl:dr[TLDR] </h2

    (domain readiness app) a free service to tx-authenticated users of my .dom TLD that provides notifications and management of DNS and <a href=http://dnseppus.meansofproduction.biz/doc/about>EPP</a> for domain operators.

  4. tl:dr[*ledger] </h2

    provides same device coverage for the <a href=http://ledger-cli.org>*ledger</a> ecosys (hledger, c++ ledger, etc.) with interface to SQL Ledger (my current ERP core of choice) and Quickbooks.

No Entrapment, No Freebies

The dr component is useful for any domain using the standard internet systems programs and task and ledger apps similarly allow users to use their own backend services instead of my cloud services. In principle and in fact. However the distributed binaries are necessarily dependent on my biz infrastructure and offerings so you need to have a Developer class account to get the dev kit to make them work with your backends.

Cloud services are available at two levels, each bundled for the whole suite. These apps are included in the sameboat personal domain service offering.