products spec
13 aug 2015 8:11am
first we need to clearly define our products
products:
code/test modules - separate code modules that are can test form/function in defining particular features or feature sets
demo - a demo product only patched together with some static screen displays that indicate what the system will do; this product mainly focuses on nav & general education of what we are creating
mvp - minimal viable product; this often means different things to different people; i like to think of it as an alpha test product; something we can raise money with; something we can ask friends to test
v1.0 launch - i would define this as a beta test product; we can finally launch something to the general product, but with limited marketing behind it; because we are really just looking for feedback, so we can tweak things before we really push it with marketing $s being spent
v2.0 launch - this is the full push product
each product will inform the next in the series
we want to spend minimal $ & time at each product stage
but these two project attributes usually fight one another
the trick is to find the right balance all the time
spec:
code/test modules:
host:
first we need to decide of a host - where we will do our code dev work
joe has used yahoo! in the past
i have an active paid account still now
tall said he has an account too
we need to pick one and start setting up
if joe will do most this initial setup work then probably best we use the system he is most familiar with
test database of world of stories:
joe can do this work now
we need to create a test database of story examples
at least 4 levels deep so the full range of name/nav can be tested
we need to be able to nav back & forth from level 0 to lowest level
we just need community names & story titles
stories do not need content yet
goal here is to just be able to nav the entire world of stories
meaning to be at any standpoint in the world
sphere or story standpoints
next to integrate with our modified ge template frontend
but even prior to getting the ge template modified, we can test with a simple display
just 3-component standpoint nav object
echo standpoint position
echo items within standpoint sphere
echo display type
world
story
ge template modified:
tall mentioned the code is available for this
what code?
database too?
we need to get code operational on our own server
we need to learn its limitations
e.g. i suspect it was statically designed for the exact number of objects it presents
we need a dynamic solution that will work with any number of objects
we need to then apply/modify this code to our app
i suspect this will require new algorithm(s)
a dynamic object placement algorithm
for both global & scattered views
but maybe start with just global view
any number of items up to our 100 max limit
we must add the standpoint name/nav object
this is the primary way we will explore/nav this early world
click/tap one of the 3 components to move to a new standpoint view screen in the world of stories
be able to nav a simple test world of stories
who will do all this work?
(more coming)