Skip to main content

Development Strategy

We have one overall strategy for completing the prototype but is better managed on a small scale on each Product separately.

The development will be divided into milestones, each focusing on a different mission (e.g. refactor, redesign, etc), each milestone will consist of a series of sprints. We may from time to time interrupt the focus on a milestone to inject needed features or fix important issues.

With each milestone we will shift how we develop our apps, starting with as much out of the box and evolving to as much internal as possible.

This stratagy will be applied to each new feature that we develop, repeating the process each time.

Development Plan

The process of development will be as follows. We will work in an agile, Scrum model, in sprints of five days (Monday to Friday), each referred to as a “Sprint”. Our first focus will be the state management and API connections, we will establish all connections needed and test the models to ensure all features work properly, this will ensure all functionality is working for Milestone One and the connections and data is secure. Then we will focus on the User Experience, User Interface of BIDDY, once that is complete we will switch our focus back to State Management and improve what we originally built. We will determine what would be better off being moved to the backend and make notes for future development.

Teams​

The dev teams are devided by divisions, while you are not exclusivly working with your team, this help you stay focused when when you are asked to help another team, this also makes it clear who is your manager to assign your tasks and who you report to.

Milestones​

Milestones represent the biger picture, while sprints contain tasks from multipe products, milestome marke the coplition of a product or event a set of products with a similar target.

Milestone One​

In the first milestone we will focus on sales. There are three revenue streams from sales...

  • First, ad sales. by focuing on content we are encuraging businesses to create ads on our platform however, for them to know about us we need to focus on profiles as well.
  • Second, branded profiles sales, now that we have businesses on the platform advertising, we will offer them the option to standout with a branded profile. (optinaly we can make a branded and varified profile mandatory in order to advertive with a credit to use that money in ad budgets)
  • Third, commerce, by now we have many businesses, we will allow them to sell products and services and we will take a cut.

Priority #1​

Thses tasks are the first prioraty but the items within are not orted by priority

  • Profile

    Comple the development of Profile and ensure there is an easy way for agencies to upload data, create profile and invite thier clients in bulk (spreadsheet, api connections, etc.)

    • cource profile data by partnering with jewish phone book and marketing companies

    • crate a scrapert to fill data missing from profiles and to create new profiles of intrest

    • allow users to sugest chnages to "public" profiles (businesses, figuers, locations, etc).

    • partner with anyone who holds jewish historical data about jewish figuers like fallen solders, holocust stories, etc. (e.g. musiumes, libraries, researchers, non-profits, etc).

    • develop premium profile design

    • develop premium profile prompt, upgrade and checkout views

      reqier a primium profile in order to post products, the value is then credited in ads

  • Enable all content types one by one, create partnerships, scrapers and anything else needed to fill with nesacary data

    • Music
    • TV shows
    • Movies
    • Rcipies
    • Stories
    • Articles
    • News ...

  • Create

    Develop the create flow for each feature that is launched

  • Commerce commerce does not have to wait for content to be complte, we will look for another dev.

    • Merge the commerce frontend
    • connect commerce API to backend
    • add products to profile

  • build the home view

Priority #2​

  • Refactor & redesign all features alredy enabled
  • Build dedicated app experiances for each feature
    • Podcast
    • Music
    • Shows
    • Movies
    • News
    • Shuk
    • Cotch (paid by investor)
    • Publisher
    • Creator
    • Studio
    • Merchant
    • Advertise ...

Tech Stack​

We will use the BackBone CMS API for all content related features and WooCommerce (or BackBone Commerce if we find a backend dev) for all commerce related features, where they overlap such as auctions, we will need to plan further with devs from each team.

For a full tech stack breakdown see Tech Stack

Expected outcome​

By the end of this milestone we should have all content types released at least in beta and commerce on profiles.

note

While we focus on our milestome we should simutaniusly be refactoring any file that we touch. Cleaning up the code, breaking files and widgets into smaller parts.