Live data from Hacker News

Viewing profile — adamstep

adamstep

HN member
Joined
Thu, Oct 25, 2018, 6:02 PM UTC
HN karma
49
Public activity
33 items

About adamstep

No profile information was provided.

Recent public activity

  1. comment
    Comment #44676047

    Hyperview creator here. Yes, it sounds like the difference is that your project is directly rendering platform-native UI widgets, while Hyperview is built on top of React Native fo…

  2. comment
    Comment #37591730

    The experience using Django & htmx is very similar to using Django & Hyperview. In both cases, you are primarily working with Django views and templates to build your app. You don’…

  3. comment
    Comment #34142855

    XML, as the name implies, is extensible. An important aspect of Hyperview is that developers can create their own high-quality UI elements that can then be referenced by the backen…

  4. comment
    Comment #34142684

    There is not, but the Github repo comes with a kitchen-sink demo app that you can try: https://github.com/instawork/hyperview#2-start-the-demo-app

  5. comment
    Comment #34142676

    Theoretically yes. Since Hyperview uses React Native, you can use React Native for Web to render a Hyperview app in the web browser. However, the resulting web app won't feel at ho…

  6. comment
    Comment #34142666

    Yes, Hyperview was definitely inspired by Jasonette. Like others have mentioned, Jasonette is not maintained, and Jasonelle has moved away from the server-driven paradigm. Check ou…

  7. comment
    Comment #34142649

    It is possible. We've built apps this way (integrating Hyperview into an existing RN app). With custom behaviors, you can have actions in Hyperview screens trigger Redux actions: h…

  8. comment
    Comment #34140745

    Local interactions can be achieved with this approach by building custom components. However, a limitation of Server-driven UI is supporting interactions that update state across t…

  9. comment
    Comment #34140188

    Trivial UI updates can be handled client-side without hitting the server. Some things can be done with the standar feature if Hyperview, like hiding/showing elements. For filtering…

  10. comment
    Comment #34140105

    Hyperview probably isn’t the best fit for apps with deep platform integration. Given that it’s designed to be cross-platform and server-rendered, I think this use case would be bet…

  11. comment
    Comment #34139570

    That’s right. Under the hood, the Hyperview client is built on top of React Native. That means it can be easily extended by creating new RN components, and mapping them to a new XM…

  12. comment
    Comment #34139152

    That’s right, no native code is shipped dynamically. The dynamic part is the layout of components and styling. Many apps use this approach and refer to it as Server-driven UI (SDUI…

  13. comment
    Comment #34139138

    I’ve been thinking about adding something like this to the Hyperview client: if a response uses HTML content type, we can render the screen in a web view.

  14. comment
    Comment #34139113

    There is session storage much like in a web browser. So you can use the same cookie-based auth techniques.

  15. comment
    Comment #34138761

    Hyperview incorporates ideas from HTMX to make it easy to create dynamic apps without the need for developers to write client-side JS.

  16. comment
    Comment #34138695

    “Native” in this case refers to the fact that the interface is rendered using the system UI libraries. So you get a native feel for things like scrolling, navigation, gestures, etc…

  17. story
  18. comment
    Comment #28384382

    Thanks for the mention! We continue to invest in Hyperview to solve many of the problems presented in the article. One big difference: instead of JSON, we use XML to represent the …

  19. comment
    Comment #23195770

    Congrats on the launch! As a big user of Intercooler, I'm curious about which features you considered mistakes, or which ideas didn't work out as well as you expected. My own libra…

  20. comment
    Comment #22839257

    Nice work! I’ve been looking for a visualization like this. My only feedback would be to make the non-cumulative view the default. Given the name of the site, it makes sense to hig…

  21. comment
    Comment #21400433

    Author here. The meta-point of my post is that different formats have their advantages and disadvantages, and it's good to understand those when deciding on what's appropriate for …

  22. comment
    Comment #21195985

    I totally agree, the benefit of NoJS comes from not needing to write custom code in order to implement a feature. Thanks for the link to that list of other NoJS libraries. If you h…

  23. comment
    Comment #21195875

    That's right. By including the Intercooler.js library, we don't need to write custom JS when developing features in our web app. We can take full advantage of JS APIs like AJAX and…

  24. comment
    Comment #21195827

    Like I mentioned in the article, our main motivation is increased productivity. By avoiding JS for feature development, we write fewer lines of code and ship faster. Better maintai…

  25. comment
    Comment #21186476

    Thanks! There's so much potential there, we're excited to push the limits.