Skip to main content

AppDirective™

Directives go in, apps come out.™

An app to get software created without managing developers

How it works:
  1. Go to AppDirective and become a CodeBoss™
  2. Provide a simple description of your problem to launch a directive
  3. Sit back and enjoy reviewing and approving contributions
AppDirective uses advanced technology to get the software developed that you want, without you ever needing to hire a developer.

Note: This app is currently about halfway built, at the time this is being posted. We plan to have it completed soon. Until then, please leave a comment or contact us to become a boss.

Q&A:

Q: How do I get recognized for being original?
A: When you launch a directive, you stake a claim to your app idea on a first-come, first-served basis. AppDirective™ keeps an unchanging public record that you deserve credit for claiming the idea at that time.

Q: Does launching a directive protect my legal rights?
A: No. Directives do not provide any legal protection for Intellectual Property (IP) rights. For assistance with obtaining IP protections, please consult a lawyer.

Q: What if I get bored of being boss?
A: Other people can offer to pay you to take over your directive, depending on how popular it is.

Q: What's in it for AppDirective™?
A: AppDirective™ facilitates trading between developers at various prices, during development. AppDirective™ earns income by charging a small (1%) commission per trade.

Q: Can I use AppDirective™ for secret or closed source projects?
A: No. AppDirective™ is based on public source code, because we believe in the freedom to collaborate. (An AppDirective™ app can safely use secret data, but the app itself cannot be secret.) Also, while you cannot use AppDirective™ to develop software that is part of closed source itself, you may still use it to develop related software such as environments and tools, as long as you keep them separate.

If you simply need valuable software developed to solve a problem, use AppDirective™. If you have a project for software that must be restricted from being Open Source or disclosed for some reason, unfortunately, you cannot use AppDirective™ to have it developed, at this time.

Please leave a comment with your thoughts, or contact us with any questions or concerns.

Author: Isaac Serafino on behalf of Serafino Software™
Originally Posted: March 1, 2018



Advanced Technical Details (For Developers Only):

Use ballots and contributions to exercise your creative talents as you think best.

Ballots:

  1. Find a directive that fits your interests
  2. Buy and sell ballots for that directive to earn incentives as the app is developed
  3. Use ballots to elect new bosses
    • You get to cast one vote per ballot
    • You can vote for yourself or for any boss whom you trust to represent your interests
    • Bosses have control to change the directive and approve contributions

Contributions:

Contribute a repository for the solution
  1. Find or create a repository to contain the solution for the directive
    1. Collaborators will develop the solution through the approved repository
  2. Propose the repository to the boss of the directive, to build the value of the directive
  3. The boss has control to approve or deny the proposal
  4. AppDirective™ links the repository to the directive when the boss approves it

Comments

Popular posts from this blog

Shared Project Manifesto Version 2

Contents:IntroductionLaunchTradeRewardDevelopVoteHarvest 1. Introduction IP (Intellectual Property) is a great asset but it is hard to produce well. We hypothesize that a market to facilitate shared projects would make it easy to produce IP better.


The market contains projects. Each project has one admin and a number of traders and developers. One user can have any combination of roles at the same time. For example, a user may be an admin and also a trader, or a trader and also a developer. ProjectsUsersAdmin: Provides ideas in exchange for controlTraders: Provide incentives in exchange for growthDevelopers: Provide IP in exchange for incentives 2. Launch When somebody came up with an idea for an IP product, they could create a project for it on the market. That person would be the admin.
The market would record the time the admin launched the project. That lasting record could provide for the admin to claim credit for the project idea, on a first-come, first-served basis. This recogn…

Contact Codes Lite™

CCL (Contact Codes Lite™) would be a software product to help people exchange many kinds of contact information much more easily. CCL would do this by providing users with relatively simple contact codes. The users could distribute the codes to many people in many ways. Then, a person who received a contact code could use it to retrieve the original person's contact information through CCL.

For example, many people still exchange business cards. Retrieving various information from the cards can be time consuming and error prone, especially when there are many cards. Also, when somebody updates their information, the information from the card is no longer valid.

Other good examples for usage of contact codes include:
On a slide in a presentationIn email signaturesOn name tagsIn applications that provide limited space for profile informationWhenever you want to provide easy access to many different contact options without listing each
The main thing that would make CCL different from…

Fog Machine

Fog Machine™ (named because fog is like a cloud, on the ground) is a software product to provide cloud services to customers without a cloud service provider. The problem with the traditional cloud is that it requires a provider. Fog Machine™ would run cloud "nodes" in idle system resources on ordinary user's devices. This would be a peer to peer system in which each connected device would be a peer.

It would support standard cloud APIs (perhaps Cloud Foundry?) and it would be easy to port cloud apps to it off providers such as Google cloud, Azure, or AWS--or maybe it would be effortless for apps that were already portable through compliance with open standards.

We might use encryption for privacy, redundancy for reliability, and remuneration/incentive for resource consistency. The showstopper (critical assumption) is that the synergy would be sufficient to significantly surpass the overhead, and provide competitive performance for at least some types of cloud applicat…

Please Comment

Have you ever heard of a similar idea? What challenges might an idea run into? How might you like to be involved? Comment to add your voice to each idea.