truesraka.blogg.se

Chrome extensions hoversee
Chrome extensions hoversee










chrome extensions hoversee
  1. #CHROME EXTENSIONS HOVERSEE INSTALL#
  2. #CHROME EXTENSIONS HOVERSEE FULL#

They're more patient and willing to do something extra like install and explore an extension, especially if their friends recommend it. The 1% have experienced and understand the basics and want more. We want every visitor to be able to explore and use certain tools, but we also want to keep things relatively simple and not overwhelm new users.

chrome extensions hoversee

If something is for the 99%, it should be part of the core. Most of the features and functions we're talking about are only for the third group, the 1%. 1% form the real community and do most of the work.They're just viewing our tree (and seeing the ads that pay for it). But I don't think that's such a big problem here. One of biggest objections to extensions is that most users will never install them. You can also do things that can't be done with an isolated app.ĪN ALMOST-REQUIRED EXTENSION FOR ADVANCED MEMBERS? The great advantage of an extension over an app, I think, is that it can overlay the main website and the member experiences them together. And there is one we've had for years, WikiTree X. But I think this vision will work best for alternate tree views, not for other sorts of tools.Ī few of you have created browser extensions. Also, Jamie has been refactoring Justin York's old dynamic family tree code with an eye towards eventually making it a platform for navigating between apps. Some developers have worked hard to keep their UI consistent with the main site, and have also integrated their app with other apps (see especially Greg Clarke's fan chart and associated apps). One problem with extending WikiTree through apps is that it's hard to create an integrated user experience. Some amazing apps and extensions have been created and now add significantly to the member experience. We've known all this for a long time, which is why we have encouraged independent developers and continually expand our APIs. And every one we do add increases the weight of what we have to maintain in the future. We don't have much time to work on new features. As it is, most of our technical resources go into supporting the servers and keeping existing features and functions running. However, if we keep the organization the way it is, we can't keep growing in both size and complexity. For various reasons, I think it's best for our community and our mission. It's still a virtual company with no full-time employees. But the size of the business behind WikiTree has not. The size of our tree, our active member base, and our site traffic have all grown steadily over our 14-year history.

#CHROME EXTENSIONS HOVERSEE FULL#

I want to give the full context.Īs I've said in the past, my vision is to keep the technical core of WikiTree as simple as possible. What do you think of the idea of a project-managed browser extension? Would you contribute to it? WikiTree Apps members and other developers,












Chrome extensions hoversee