f1xska

<h1>Helpers</h1>
<div class="level1">

</div>

<h2>About</h2>
<div class="level2">

<p>
The Helpers project's objective is to link small Businesses or people in need of helping hand and people who can help. The jobs usually span several hours and are paid on higher than average basis.<br/>

Potential areas: Babysitter, Waiter, Leaflets/Magnets/Ads distributors, Movers, Delivery service etc.
</p>

<p>
The project's purpose is to build something useful to users, with hope that some elements might be used for much more ambitious F1x project.
</p>

</div>

<h2>User Interface Screens</h2>
<div class="level2">
<ul>
<li class="level1 node"> User registration: Name, Last Name, login, password, telegram ID<ul>
<li class="level3"> The telegram ID is to send individual messages, by bot, that will produce unique sound and allow user to do short answers.</li>
</ul>
</li>
<li class="level1"> Users might specify factors on their profile, such as: Gender, GeoLocation, Languages, Driving License(s), Minimum Hourly and Total Wage, Car/Scooter Availability</li>
<li class="level1 node"> Interactive Positions Posting<ul>
<li class="level3"> Posting user immediately sees how many candidates are "covered", by his factors, live</li>
<li class="level3 node"> Sending is staggered, e.g. offers are sent to "Best" candidates first. Sending stops once given amount of candidates agree to take on the job and the Position is marked as covered.<ul>
<li class="level4"> Candidates are ranked by sum of Matching Factors, multiplied by Factor weight</li>
<li class="level4"> Candidates receive offers on Telegram Bot and can answer either "No", "Not sure", "Accept".</li>
</ul>
</li>
<li class="level3"> Posting user sees results of his "call-up" and might change Factors (most likely Hourly Wage). In this case the new offer is sent to users who answered "Not sure"</li>
</ul>
</li>
<li class="level1 node"> Feedback - must be as neutral as possible (to avoid legal issues)<ul>
<li class="level3"> User might grade other User, using single grade on scale -10 to 10, where 0 is neutral and default</li>
</ul>
</li>
</ul>

</div>

<h2>Open questions</h2>
<div class="level2">
<ul>
<li class="level1"> How to rank mobility? For many users, having to take more than one bus is deal killer. For such users the key is to predict travel complications. <br/>
Need to do interview with users to understand this deeper. <br/>
May be to have exponential Mobility score? Like 1-10 traveling distance by foot, 11-20 by bike/electric scooter, 21-30 by bus, 31-40 by car?</li>
<li class="level1"> Factor Weight - how to estimate its weight?</li>
<li class="level1"> Need to create portfolio of use cases, based on history of offers.</li>
</ul>

</div>

<h2>Architecture</h2>
<div class="level2">
<ul>
<li class="level1"> Need to plan architecture, so it would be easy to reuse parts for the F1x</li>
</ul>

</div>

<h2>Monetization</h2>
<div class="level2">
<ul>
<li class="level1"> Free Users can have up to 3 covered positions or "hires". After that they need to pay small monthly fee.</li>
</ul>

</div>

Enable Complex Tables Editor Height px Turn supplementary image paste support on

Edit summary: Minor changes