Skip to content

Home and Beacon separation #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Turmi0 opened this issue Dec 12, 2017 · 2 comments
Open

Home and Beacon separation #16

Turmi0 opened this issue Dec 12, 2017 · 2 comments

Comments

@Turmi0
Copy link
Contributor

Turmi0 commented Dec 12, 2017

Is Home and Beacon described well enough as a separated components?

For example "Works with Raspberry Pi" means only Beacons but it is not mentioned in the text.

@eemil
Copy link

eemil commented Dec 12, 2017

The entire page is fairly beacon-heavy. Until the "Get started" section, Home is only mentioned a few times and somewhat ambiguously ("Beacon calls Home"). This isn't necessarily a bad thing, since Beacon is the part of our product that the customer can see and feel, and what they will be deploying.

I think most readers will infer that anything written applies to Beacon, they might not even realize that Home is a component that they could deploy themselves.

@Turmi0
Copy link
Contributor Author

Turmi0 commented Dec 12, 2017

Thats true. On the other hand, price is currently based on number of Home -instances .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants