# InstaPy ROADMAP
## Intro
This document have the intention to be a development guide for the next InstaPy iteration.
## Why do we need it ?
1. It's a good entry point for new incommers
2. Everyone goes to the same direction
3. We set clear goals
## Where are we now ?
fsgewrsg
**[bad]**
1. The code and documentation is a bit complex to manage
2. Community posted issues rarely get answered by core-devs or active users in the project.
3. Lack of testing has led to the tool being depractated in several instances, and no way to quickly indentify bugs.
**[good]**
1. The best open source Instagram tool.
2. A lot of great features.
3. Big community with several active developers.
## Where do you want to go ?
1. Easier tool to final user (Full setup with a GUI / InstaPy Dashboard)
2. [Easier install process](https://github.com/timgrossmann/InstaPy/projects/3)
3. Good analytics tool to track progress and effectivity (InstaPy Dashboard)
4. Release schema
5. Have stable and (beta version or development version)
6. Leveraging the Instagram internal features, like suggestions, better (that's not much clear for me..)
7. Writing test for easier testing of PRs
8. Community backed feature requests with bounties on Bountysource
9. Better community engagement by prioritizing community wishes
> [name=converge: let's set a small marketing team ? some people that want to contribute, but doesnt code, they can make monthly newlestter about InstaPy.]
> [name=timgrossmann: Absolutely, that's what I was thinking about. We just need to find a few people who are interested. If you're reading this and you are, reach out to us in discord.]
> [name=synchronizing: I agree with this as well. If money is something that the project wants to eventually achieve, we can use the open-souce-pay-us-template that every large project uses: create a stable open source release, and then open a live platform (i.e. InstaPy.io) that allows users to pay a monthly payment for access to a web app that gives all the benefits of the open source project, but without the headache of set-up. Charge a small fee of $5 dollars a month for something like 10 accounts -- or how much ever to balance AWS fees and profit. Create custom plans for businesses, and begin a side-business for managing large corporate accounts on Insta looking to increase engagement.]
11. Having InstaPy ambassador with quickly growing accounts. I recently talked to a friend of mine who's following a pretty new account that grew incredibly quick. No one knows how she can do it this quickly with real engagment.
Finding someone who's interesting in rapidly growing their account with good support could show people what is capable when using InstaPy which in return would be good advertisement for InstaPy.
>[name=converge: could you explain a little more ?]
13. InstaPy official Homepage
>[name=converge: it's a big step, just don't know if this is the moment.]
>[name=timgrossmann: True, I think we should only do this once we have a working gui and a less error prune version. I think we could generate some income from this which would help with adding bounties to task or giving back to the core contributors.]
>[name=synchronizing: I would say that at the very least it would be benefitial to buy the domain and hold it as a simple directory for documentation of the app. Doesn't have to be extensive, but it would be benefitial. ]
14. Less complex documentation
>[name=christophe-duc: 15. Replace current block actions by a finite state machine where all actions are possible all the time. The state machine defines what to do randomly and according to the user configured actions and amounts.]
## How we will get there ?
1. Building a new GUI on top of the API.json definition that allows easy generative creation of the GUI.
- Extensible by InstaPy contributors without having to extend actual GUI code
2. Getting rid of separate chromedriver download and installing python dependencies with "one button click" or automatically checking them when running InstaPy for the first time.
3. Extending @converge's InstaPy-Dashboard (https://github.com/converge/instapy-dashboard) with more analytical features. Adding D3 for simple graph creation.
>[name=synchronizing Docker-compose, in my honest opinion, should be the way to go for this case. Package it as a docker container and shoot it up to the Docker library. Docker will remove everyones headache of "how do I do this," specially with a proper GUI implemented on top of it.]
4. Considering the amount of updates we stInstaPy ROADMAP
Intro
This document have the intention to be a development guide for the next InstaPy iteration.
Why do we need it ?
It’s a good entry point for new incommers
Everyone goes to the same direction
We set clear goals
Where are we now ?
fsgewrsg
[bad]
The code and documentation is a bit complex to manage
Community posted issues rarely get answered by core-devs or active users in the project.
Lack of testing has led to the tool being depractated in several instances, and no way to quickly indentify bugs.
[good]
The best open source Instagram tool.
A lot of great features.
Big community with several active developers.
Where do you want to go ?
Easier tool to final user (Full setup with a GUI / InstaPy Dashboard)
Easier install process
Good analytics tool to track progress and effectivity (InstaPy Dashboard)
Release schema
Have stable and (beta version or development version)
Leveraging the Instagram internal features, like suggestions, better (that’s not much clear for me…)
Writing test for easier testing of PRs
Community backed feature requests with bounties on Bountysource
Better community engagement by prioritizing community wishes
converge: let's set a small marketing team ? some people that want to contribute, but doesnt code, they can make monthly newlestter about InstaPy.
timgrossmann: Absolutely, that's what I was thinking about. We just need to find a few people who are interested. If you're reading this and you are, reach out to us in discord.
synchronizing: I agree with this as well. If money is something that the project wants to eventually achieve, we can use the open-souce-pay-us-template that every large project uses: create a stable open source release, and then open a live platform (i.e. InstaPy.io) that allows users to pay a monthly payment for access to a web app that gives all the benefits of the open source project, but without the headache of set-up. Charge a small fee of $5 dollars a month for something like 10 accounts -- or how much ever to balance AWS fees and profit. Create custom plans for businesses, and begin a side-business for managing large corporate accounts on Insta looking to increase engagement.
Having InstaPy ambassador with quickly growing accounts. I recently talked to a friend of mine who’s following a pretty new account that grew incredibly quick. No one knows how she can do it this quickly with real engagment.
Finding someone who’s interesting in rapidly growing their account with good support could show people what is capable when using InstaPy which in return would be good advertisement for InstaPy.
converge: could you explain a little more ?
InstaPy official Homepage
converge: it's a big step, just don't know if this is the moment.
timgrossmann: True, I think we should only do this once we have a working gui and a less error prune version. I think we could generate some income from this which would help with adding bounties to task or giving back to the core contributors.
synchronizing: I would say that at the very least it would be benefitial to buy the domain and hold it as a simple directory for documentation of the app. Doesn't have to be extensive, but it would be benefitial.
Less complex documentation
christophe-duc: 15. Replace current block actions by a finite state machine where all actions are possible all the time. The state machine defines what to do randomly and according to the user configured actions and amounts.
How we will get there ?
Building a new GUI on top of the API.json definition that allows easy generative creation of the GUI.
Extensible by InstaPy contributors without having to extend actual GUI code
Getting rid of separate chromedriver download and installing python dependencies with “one button click” or automatically checking them when running InstaPy for the first time.
Extending @converge’s InstaPy-Dashboard (https://github.com/converge/instapy-dashboard)InstaPy ROADMAP
Intro
This document have the intention to be a development guide for the next InstaPy iteration.
Why do we need it ?
It’s a good entry point for new incommers
Everyone goes to the same direction
We set clear goals
Where are we now ?
fsgewrsg
[bad]
The code and documentation is a bit complex to manage
Community posted issues rarely get answered by core-devs or active users in the project.
Lack of testing has led to the tool being depractated in several instances, and no way to quickly indentify bugs.
[good]
The best open source Instagram tool.
A lot of great features.
Big community with several active developers.
Where do you want to go ?
Easier tool to final user (Full setup with a GUI / InstaPy Dashboard)
Easier install process
Good analytics tool to track progress and effectivity (InstaPy Dashboard)
Release schema
Have stable and (beta version or development version)
Leveraging the Instagram internal features, like suggestions, better (that’s not much clear for me…)
Writing test for easier testing of PRs
Community backed feature requests with bounties on Bountysource
Better community engagement by prioritizing community wishes
converge: let's set a small marketing team ? some people that want to contribute, but doesnt code, they can make monthly newlestter about InstaPy.
timgrossmann: Absolutely, that's what I was thinking about. We just need to find a few people who are interested. If you're reading this and you are, reach out to us in discord.
synchronizing: I agree with this as well. If money is something that the project wants to eventually achieve, we can use the open-souce-pay-us-template that every large project uses: create a stable open source release, and then open a live platform (i.e. InstaPy.io) that allows users to pay a monthly payment for access to a web app that gives all the benefits of the open source project, but without the headache of set-up. Charge a small fee of $5 dollars a month for something like 10 accounts -- or how much ever to balance AWS fees and profit. Create custom plans for businesses, and begin a side-business for managing large corporate accounts on Insta looking to increase engagement.
Having InstaPy ambassador with quickly growing accounts. I recently talked to a friend of mine who’s following a pretty new account that grew incredibly quick. No one knows how she can do it this quickly with real engagment.
Finding someone who’s interesting in rapidly growing their account with good support could show people what is capable when using InstaPy which in return would be good advertisement for InstaPy.
converge: could you explain a little more ?
InstaPy official Homepage
converge: it's a big step, just don't know if this is the moment.
timgrossmann: True, I think we should only do this once we have a working gui and a less error prune version. I think we could generate some income from this which would help with adding bounties to task or giving back to the core contributors.
synchronizing: I would say that at the very least it would be benefitial to buy the domain and hold it as a simple directory for documentation of the app. Doesn't have to be extensive, but it would be benefitial.
Less complex documentation
christophe-duc: 15. Replace current block actions by a finite state machine where all actions are possible all the time. The state machine defines what to do randomly and according to the user configured actions and amounts.
How we will get there ?
Building a new GUI on top of the API.json definition that allows easy generative creation of the GUI.
Extensible by InstaPy contributors without having to extend actual GUI code
Getting rid of separate chromedriver download and installing python dependencies with “one button click” or automatically checking them when running InstaPy for the first time.
Extending @converge’s InstaPy-Dashboard (https://github.com/converge/instapy-dashboard) with more analytical features. Adding D3 for simple graph creation.
synchronizing Docker-compose, in my honest opinion, should be the way to go for this case. Package it as a docker container and shoot it up to the Docker library. Docker will remove everyones headache of "how do I do this," specially with a proper GUI implemented on top of it.
Considering the amount of updates we stInstaPy ROADMAP
Intro
This document have the intention to be a development guide for the next InstaPy iteration.
Why do we need it ?
It’s a good entry point for new incommers
Everyone goes to the same direction
We set clear goals
Where are we now ?
fsgewrsg
[bad]
The code and documentation is a bit complex to manage
Community posted issues rarely get answered by core-devs or active users in the project.
Lack of testing has led to the tool being depractated in several instances, and no way to quickly indentify bugs.
[good]
The best open source Instagram tool.
A lot of great features.
Big community with several active developers.
Where do you want to go ?
Easier tool to final user (Full setup with a GUI / InstaPy Dashboard)
Easier install process
Good analytics tool to track progress and effectivity (InstaPy Dashboard)
Release schema
Have stable and (beta version or development version)
Leveraging the Instagram internal features, like suggestions, better (that’s not much clear for me…)
Writing test for easier testing of PRs
Community backed feature requests with bounties on Bountysource
Better community engagement by prioritizing community wishes
converge: let’s set a small marketing team ? some people that want to contribute, but doesnt code, they can make monthly newlestter about InstaPy.
timgrossmann: Absolutely, that’s what I was thinking about. We just need to find a few people who are interested. If you’re reading this and you are, reach out to us in discord.
synchronizing: I agree with this as well. If money is something that the project wants to eventually achieve, we can use the open-souce-pay-us-template that every large project uses: create a stable open source release, and then open a live platform (i.e. InstaPy.io) that allows users to pay a monthly payment for access to a web app that gives all the benefits of the open source project, but without the headache of set-up. Charge a small fee of $5 dollars a month for something like 10 accounts – or how much ever to balance AWS fees and profit. Create custom plans for businesses, and begin a side-business for managing large corporate accounts on Insta looking to increase engagement.
Having InstaPy ambassador with quickly growing accounts. I recently talked to a friend of mine who’s following a pretty new account that grew incredibly quick. No one knows how she can do it this quickly with real engagment.
Finding someone who’s interesting in rapidly growing their account with good support could show people what is capable when using InstaPy which in return would be good advertisement for InstaPy.
converge: could you explain a little more ?
InstaPy official Homepage
converge: it’s a big step, just don’t know if this is the moment.
timgrossmann: True, I think we should only do this once we have a working gui and a less error prune version. I think we could generate some income from this which would help with adding bounties to task or giving back to the core contributors.
synchronizing: I would say that at the very least it would be benefitial to buy the domain and hold it as a simple directory for documentation of the app. Doesn’t have to be extensive, but it would be benefitial.
Less complex documentation
christophe-duc: 15. Replace current block actions by a finite state machine where all actions are possible all the time. The state machine defines what to do randomly and according to the user configured actions and amounts.
How we will get there ?
Building a new GUI on top of the API.json definition that allows easy generative creation of the GUI.
Extensible by InstaPy contributors without having to extend actual GUI code
Getting rid of separate chromedriver download and installing python dependencies with “one button click” or automatically checking them when running InstaPy for the first time.
Extending @converge’s InstaPy-Dashboard (https://github.com/converge/instapy-dashboard)ill have to make, releasing versions seems to be only reasonable when we have more stable versions (see 5.)
Automatic detection of changed HTML-Elements through a diffing of the page structure from the last run to the new one (see https://github.com/google/incremental-dom)
One option for the suggestions might be to engage in specific ways:
go to some post of an account
go to the comments
go to the accounts of the commenter
interact with the followers of that commenter.
…
Making people and espacially businesses realize that they can contribute to the project by showing respectill have to make, releasing versions seems to be only reasonable when we have more stable versions (see 5.)
5. Automatic detection of changed HTML-Elements through a diffing of the page structure from the last run to the new one (see https://github.com/google/incremental-dom)
6. One option for the suggestions might be to engage in specific ways:
- go to some post of an account
- go to the comments
- go to the accounts of the commenter
- interact with the followers of that commenter.
7. ...
8. Making people and espacially businesses realize that they can contribute to thInstaPy ROADMAP
Intro
This document have the intention to be a development guide for the next InstaPy iteration.
Why do we need it ?
It’s a good entry point for new incommers
Everyone goes to the same direction
We set clear goals
Where are we now ?
fsgewrsg
[bad]
The code and documentation is a bit complex to manage
Community posted issues rarely get answered by core-devs or active users in the project.
Lack of testing has led to the tool being depractated in several instances, and no way to quickly indentify bugs.
[good]
The best open source Instagram tool.
A lot of great features.
Big community with several active developers.
Where do you want to go ?
Easier tool to final user (Full setup with a GUI / InstaPy Dashboard)
Easier install process
Good analytics tool to track progress and effectivity (InstaPy Dashboard)
Release schema
Have stable and (beta version or development version)
Leveraging the Instagram internal features, like suggestions, better (that’s not much clear for me…)
Writing test for easier testing of PRs
Community backed feature requests with bounties on Bountysource
Better community engagement by prioritizing community wishes
converge: let's set a small marketing team ? some people that want to contribute, but doesnt code, they can make monthly newlestter about InstaPy.
timgrossmann: Absolutely, that's what I was thinking about. We just need to find a few people who are interested. If you're reading this and you are, reach out to us in discord.
synchronizing: I agree with this as well. If money is something that the project wants to eventually achieve, we can use the open-souce-pay-us-template that every large project uses: create a stable open source release, and then open a live platform (i.e. InstaPy.io) that allows users to pay a monthly payment for access to a web app that gives all the benefits of the open source project, but without the headache of set-up. Charge a small fee of $5 dollars a month for something like 10 accounts -- or how much ever to balance AWS fees and profit. Create custom plans for businesses, and begin a side-business for managing large corporate accounts on Insta looking to increase engagement.
Having InstaPy ambassador with quickly growing accounts. I recently talked to a friend of mine who’s following a pretty new account that grew incredibly quick. No one knows how she can do it this quickly with real engagment.
Finding someone who’s interesting in rapidly growing their account with good support could show people what is capable when using InstaPy which in return would be good advertisement for InstaPy.
converge: could you explain a little more ?
InstaPy official Homepage
converge: it's a big step, just don't know if this is the moment.
timgrossmann: True, I think we should only do this once we have a working gui and a less error prune version. I think we could generate some income from this which would help with adding bounties to task or giving back to the core contributors.
synchronizing: I would say that at the very least it would be benefitial to buy the domain and hold it as a simple directory for documentation of the app. Doesn't have to be extensive, but it would be benefitial.
Less complex documentation
christophe-duc: 15. Replace current block actions by a finite state machine where all actions are possible all the time. The state machine defines what to do randomly and according to the user configured actions and amounts.
How we will get there ?
Building a new GUI on top of the API.json definition that allows easy generative creation of the GUI.
Extensible by InstaPy contributors without having to extend actual GUI code
Getting rid of separate chromedriver download and installing python dependencies with “one button click” or automatically checking them when running InstaPy for the first time.
Extending @converge’s InstaPy-Dashboard (https://github.com/converge/instapy-dashboard) with more analytical features. Adding D3 for simple graph creation.
synchronizing Docker-compose, in my honest opinion, should be the way to go for this case. Package it as a docker container and shoot it up to the Docker library. Docker will remove everyones headache of "how do I do this," specially with a proper GUI implemented on top of it.
Considering the amount of updates we stInstaPy ROADMAP
Intro
This document have the intention to be a development guide for the next InstaPy iteration.
Why do we need it ?
It’s a good entry point for new incommers
Everyone goes to the same direction
We set clear goals
Where are we now ?
fsgewrsg
[bad]
The code and documentation is a bit complex to manage
Community posted issues rarely get answered by core-devs or active users in the project.
Lack of testing has led to the tool being depractated in several instances, and no way to quickly indentify bugs.
[good]
The best open source Instagram tool.
A lot of great features.
Big community with several active developers.
Where do you want to go ?
Easier tool to final user (Full setup with a GUI / InstaPy Dashboard)
Easier install process
Good analytics tool to track progress and effectivity (InstaPy Dashboard)
Release schema
Have stable and (beta version or development version)
Leveraging the Instagram internal features, like suggestions, better (that’s not much clear for me…)
Writing test for easier testing of PRs
Community backed feature requests with bounties on Bountysource
Better community engagement by prioritizing community wishes
converge: let’s set a small marketing team ? some people that want to contribute, but doesnt code, they can make monthly newlestter about InstaPy.
timgrossmann: Absolutely, that’s what I was thinking about. We just need to find a few people who are interested. If you’re reading this and you are, reach out to us in discord.
synchronizing: I agree with this as well. If money is something that the project wants to eventually achieve, we can use the open-souce-pay-us-template that every large project uses: create a stable open source release, and then open a live platform (i.e. InstaPy.io) that allows users to pay a monthly payment for access to a web app that gives all the benefits of the open source project, but without the headache of set-up. Charge a small fee of $5 dollars a month for something like 10 accounts – or how much ever to balance AWS fees and profit. Create custom plans for businesses, and begin a side-business for managing large corporate accounts on Insta looking to increase engagement.
Having InstaPy ambassador with quickly growing accounts. I recently talked to a friend of mine who’s following a pretty new account that grew incredibly quick. No one knows how she can do it this quickly with real engagment.
Finding someone who’s interesting in rapidly growing their account with good support could show people what is capable when using InstaPy which in return would be good advertisement for InstaPy.
converge: could you explain a little more ?
InstaPy official Homepage
converge: it’s a big step, just don’t know if this is the moment.
timgrossmann: True, I think we should only do this once we have a working gui and a less error prune version. I think we could generate some income from this which would help with adding bounties to task or giving back to the core contributors.
synchronizing: I would say that at the very least it would be benefitial to buy the domain and hold it as a simple directory for documentation of the app. Doesn’t have to be extensive, but it would be benefitial.
Less complex documentation
christophe-duc: 15. Replace current block actions by a finite state machine where all actions are possible all the time. The state machine defines what to do randomly and according to the user configured actions and amounts.
How we will get there ?
Building a new GUI on top of the API.json definition that allows easy generative creation of the GUI.
Extensible by InstaPy contributors without having to extend actual GUI code
Getting rid of separate chromedriver download and installing python dependencies with “one button click” or automatically checking them when running InstaPy for the first time.
Extending @converge’s InstaPy-Dashboard (https://github.com/converge/instapy-dashboard)ill have to make, releasing versions seems to be only reasonable when we have more stable versions (see 5.)
Automatic detection of changed HTML-Elements through a diffing of the page structure from the last run to the new one (see https://github.com/google/incremental-dom)
One option for the suggestions might be to engage in specific ways:
go to some post of an account
go to the comments
go to the accounts of the commenter
interact with the followers of that commenter.
…
- [ ] Making people and espacially businesses realize that they can contribute to the project by showing respecte project by showing respect to the developers by backing features with money.
9. Creating weekly/monthly ranking lists of features and wishes the community wants
10. Finding people with good content that are interested in automation. Using them as examples of what InstaPy can do
11. Adding a homepage for InstaPy (which later on includes download link for InstaPy - once released). Maybe advertising to create some revenue to be put back into InstaPy.
12. (14) Organize our document in Basic and Advanced features (check it also: https://gist.github.com/joyrexus/16041f2426450e73f5df9391f7f7ae5f)
13. End python 2.7 support
14. Fix QS to be aligend to ANY flow scenario and not based on current running function
15. Browser Class. Chrome/Firefox should have a separate class from instapy, and should handle executions/errors and must have a recovery method that WILL NOT fail the instapy flow.
16. instagram hack
Google Drive
Gist
Clipboard
Sign in with Wallet
