Tl;dr: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
|||
| Line 2: | Line 2: | ||
<blockquote> | <blockquote> | ||
<br><br> | <br><br> | ||
<h2>tl;dr ...</h2> | <h2>"tl;dr" a marque naming ...</h2> | ||
== | == A 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. | 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. | ||
Revision as of 12:09, 9 March 2020
"tl;dr" a marque naming ...
A 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.
