James Ide

2.8K posts

James Ide banner
James Ide

James Ide

@JI

Co-founder @Expo

California, USA Katılım Temmuz 2010
100 Takip Edilen5.8K Takipçiler
Sabitlenmiş Tweet
James Ide
James Ide@JI·
Expo’s Series B lets us build + More developer success for our world-class customers + More products to unlock that success + More capacity to meet the demand for our products and services We are also excited to continue collaborating with other great companies, and for the Expo SDK and services to work well with even more libraries, products, and integrations from others. We care and work to be a great partner to great partners. I’m proud of what we’ve built, from what started in a room w/@ccheever and is now a global team over 60 people strong. This is an energizing time to be at @Expo!
Expo@expo

🙌 Expo is the best it's ever been, and it's about to get a lot better. We raised a Series B so we can go faster on the things that matter to you: faster builds, smoother native integrations, and the services to make end-to-end app development a delightful experience. There is a lot of work to do. This round led by @Georgian_io puts us in position to go do it!

English
2
11
71
5.6K
James Ide retweetledi
Chain React (July 30–31, 2026)
Chain React (July 30–31, 2026)@ChainReactConf·
🎤 Announcing: Charlie Cheever If you're in tech, you know @ccheever. Charlie's the co-founder of @expo and one of the biggest driving forces behind React Native!! He's speaking at Chain React in Portland and we want to see you there! 🎟️ ti.to/chainreact/cha…
Chain React (July 30–31, 2026) tweet media
English
2
10
31
3.5K
James Ide retweetledi
Christian Falch
Christian Falch@chrfalch·
Looking forward to start talking more about the SPM transition in React Native. It’s going to be big. #appjsconf
English
6
8
103
17.5K
Seth Webster
Seth Webster@sethwebster·
I joined Expo.
Expo@expo

For years @sethwebster led the React team at @Meta - in that time React became the standard for web. Today we are thrilled to announce that Seth has joined Expo as our Chief Developer Evangelist. His vision, talent, and experience will make a massive impact on Expo and on the whole world of mobile development. Today is a good day. Thanks to @thenewstack and @psawers for the interview ↓

English
32
14
413
25K
Expo
Expo@expo·
For years @sethwebster led the React team at @Meta - in that time React became the standard for web. Today we are thrilled to announce that Seth has joined Expo as our Chief Developer Evangelist. His vision, talent, and experience will make a massive impact on Expo and on the whole world of mobile development. Today is a good day. Thanks to @thenewstack and @psawers for the interview ↓
Expo tweet media
English
32
26
483
43.4K
James Ide
James Ide@JI·
@theo Incidentally a similar path is how GCP became a cloud provider I can’t recommend anymore despite using them.
English
0
0
2
281
Daehyeon 대현
Daehyeon 대현@DaehyeonMun·
Finally unboxing the prize for Most Creative Winner at the @expo App Awards! 🏆 This Seneca Keyboard is a work of art a fitting reward for a project where I pushed React Native to its creative limits. I can't wait to build something amazing with it this year !!! 🔥🔥🔥
Daehyeon 대현 tweet mediaDaehyeon 대현 tweet mediaDaehyeon 대현 tweet mediaDaehyeon 대현 tweet media
English
7
3
57
7.9K
Shehzan
Shehzan@MarediaShehzan·
@JI Hey man, can you check your email? It would be great if you can have someone from your team respond to our customer service request with regards to your Expo API.
English
1
0
0
63
James Ide
James Ide@JI·
When you raise money as a startup, there are de facto terms called the NVCA Model Legal Documents. NVCA terms have you attest that your company’s proprietary code & data have never been shared with AI providers that train on your data. Services like ChatGPT, Claude, Cursor, and now GitHub Copilot now default to training on your data unless you have a business/team plan or have vigilantly disabled all sharing & training settings on a personal plan. Consider how most startups decide to expand to a team plan: individuals sign up for personal plans to try a service and then the company gets a team plan once they’re ready to commit. However, startups who plan to raise money need to be cautious about how they build a grassroots culture that encourages employees to adopt AI tools, given the now-unfriendly default policies pushed by AI model providers; the AI model providers are unaligned here with their most promising startup customers. It’s especially problematic with GitHub because it’s the norm at startups for engineers to use their existing personal GitHub accounts, which will default to letting Microsoft train on any proprietary code the personal GitHub Copilot subscription touches. Fundraising plans for startups, let alone the NVCA Model Documents, are not the only reason it’s better for data sharing & model training to default to “Disallowed”. But it’s one that people who control the purse strings should care about. nvca.org/document/nvca-…
James Ide tweet media
Gergely Orosz@GergelyOrosz

If you use GitHub (especially if you pay for it!!) consider doing this *immediately* Settings -> Privacy -> Disallow GitHub to train their models on your code. GitHub opted *everyone* into training. No matter if you pay for the service (like I do). WTH github.com/settings/copil…

English
2
0
9
1.4K
James Ide retweetledi
Tony Kim
Tony Kim@toeknee_kim·
@JI @kadikraman @expo i wonder if you could just hook up a redirect if the user agent is from an LLM so the .md knowledge doesn't have to be baked into a skill
English
1
0
0
30
Kadi Kraman 💚
Kadi Kraman 💚@kadikraman·
Did you know! You can append .md to any @expo blog or changelog post to get the content as markdown (this will also work with accept headers)
English
6
4
58
15.9K
James Ide
James Ide@JI·
Whenever a hosted service says data is visible to “only you”, this almost always means “you and the company running the service.” This is acceptable for your open-source repo or recipe ideas for what to cook tonight. But there are legal consequences for other conversation topics, like law itself and I suspect health as well. One of the most AI-forward things a democratic nation could do is establish the goal of Personal AI in Every Home, where Personal here means private and owned by the individual. Inference must run locally by default, and hosted models treated like any other hosted service. Personal AI does not need to be and will not be SOTA but it should be excellent for day-to-day intelligence. This contributes to a higher-trust society in which people trust each other more (including companies) and trust AI more. Ironically one could argue China has done the most in service of Personal AI with the best open models and weights. The U.S. absolutely can compete but I suspect the mandate needs to come from the top with a goal of Personal AI for all of its people and a mission of a high-trust society.
Moish Peltz@mpeltz

Your AI conversations aren't privileged. Yesterday, Judge Jed Rakoff ruled that 31 documents a defendant generated using an AI tool and later shared with his defense attorneys are not protected by attorney-client privilege or work product doctrine. The logic is simple: an AI tool is not an attorney. It has no law license, owes no duty of loyalty, and its terms of service explicitly disclaim any attorney-client relationship. Sharing case details with an AI platform is legally no different from talking through your legal situation with a friend (which is not privileged). You can't fix it after the fact, either. Sending unprivileged documents to your lawyer doesn't retroactively make them privileged. That's been settled law for years. It just hadn't been tested with AI until now. And here's what really hurt the defendant: the AI provider's privacy policy (Claude), in effect when he used the tool, expressly permits disclosure of user prompts and outputs to governmental authorities. There was no reasonable expectation of confidentiality. The core problem is the gap between how people experience AI and what's actually happening. The conversational interface feels private. It feels like talking to an advisor. But unless you negotiate for an enterprise agreement that says otherwise, you're inputting information into a third-party commercial platform that retains your data and reserves broad rights to disclose it. Judge Rakoff also flagged an interesting wrinkle: the defendant reportedly fed information from his attorneys into the AI tool. If prosecutors try to use these documents at trial, defense counsel could become a fact witness, potentially forcing a mistrial. Winning on privilege doesn't make the evidentiary picture simple. For anyone advising clients or managing legal risk, this is a wake-up call. AI tools are not a safe space for clients to process their counsel's advice and to regurgitate their legal strategy. Every prompt is a potential disclosure. Every output is a potentially discoverable document. So what do we do about it? First, attorneys need to be proactive. Advise clients explicitly that anything they put into an AI tool may be discoverable and is almost certainly not privileged. Put it in your engagement letters. Make it part of onboarding. Don't assume clients understand this, because most don't. Second, if clients want to use AI to help process legal issues (and they clearly will, increasingly), then let's give them a way to do it inside the privilege. Collaborative AI workspaces shared between attorney and client, where the AI interaction happens under counsel's direction and within the attorney-client relationship, can change the analysis entirely. I'm excited to be planning this kind of approach, and I think it's where the industry needs to head. storage.courtlistener.com/recap/gov.usco…

English
0
0
2
723
James Ide
James Ide@JI·
@toeknee_kim @kadikraman @expo This is our own in-house implementation which gives us more control over the markdown. The timing is certainly a coincidence!
English
3
0
2
37
Tony Kim
Tony Kim@toeknee_kim·
@kadikraman @expo Thats dope, i usually just send the url to claude code/codex. Is this due to the new cloudflare markdown change?
English
1
0
1
222
James Ide
James Ide@JI·
@zeeg Is it also true that revenue before costs = amount of money you made?
English
0
0
0
430
James Ide
James Ide@JI·
Been thinking about this a bit. In IBM's case, to their credit they have managed to keep pace with shifts in cloud. A former PM at my company used to say, "Flat is not free," with regards to growth, and IBM's stock has roughly followed QQQ (underperformed since QQQ's inception, but outperformed in the last 5 years). This is the path I foresee for most companies with shifts in AI, where they keep pace within a standard deviation of the index. Unexciting for the markets but still good for the economy. My thinking for why IBM is not magnificent, as in Mag 7, is largely ambition and hiring. I'm sure there are other paths and some Mag7 companies are good at getting B+ employees to produce A- work (not my quote). IBM has been doing AI and other futuristic technology, like quantum, for a very long time, but they're not #1 or #2. As a thought experiment on hiring, IBM would be in the zeitgeist more if they were part of the AI talent wars between OpenAI, Meta, et al. awhile back, and attract the talent aspiring to vie for #1. Kodak, on the other hand, has not kept pace whatsoever. @davidmarcus's recent post on PayPal's decline comes to mind, especially this phrase: "Choosing predictability over platform risk, again and again." x.com/davidmarcus/st… Kodak was married more to the familiar product of a film camera than the outcome for the customer, capturing moments as photos. It was a mindset problem more than a skillset problem. Going back to software companies, they're all technically capable of building agentic products; the skillset is there for the non-complacent. I expect most will have the mindset to see their product as an means to an end for the customer. They will evolve or replace their products to be more agent-powered and agent-ready, and provide better outcomes that customers can flexibly use. In contrast, I suspect companies that don't make this transition will do so out of fear. They may be afraid of losing control or revenue, or upsetting anti-AI users. But especially when those concerns are real, it's necessary to have the mindset of looking how to thread the needle. At my company I tell people, "Be the ones who replace ourselves."
English
1
0
2
147
Steven Sinofsky
Steven Sinofsky@stevesi·
@JI Maybe but why wasn’t IBM equipped to capitalize on the PC they invented or Kodak on the digital camera they invented? These were companies that invented more stuff than just about any other company.
English
2
0
21
5.8K
James Ide
James Ide@JI·
Agree: AI will increase work as computers, the internet, and mobile did. Technologies that people once said would give them back their time. But an expectation to be ever-present and ever-responding grew. It started with pagers, then email, then messaging and adjacent products like Slack. Now we are seeing people be ever-managing of agents. It’s already common to hear people say they feel they’re not being as productive as they could be if they don’t have an agent running in parallel with other tasks, including non-work time. Managing an agent for some (but not all) tasks doesn’t require focused work. You can check an agent’s state from your phone and give it a brief description of next steps. But it’s still an interruption in several ways and unlike a Slack message from another person, the agent tires only when it exhausts its token budget. The human brain needs restorative time even from menial tasks. Agents managing agents goes only so far; it is easy but not valuable to entertain the idea of more AI being the sole answer to AI. People will still be expected to manage agents, a new type of work. More generally, nearly every company has ideas for how it could do more and few will to limit their ambitions and skill ceilings to what AI alone can achieve. They will ask their employees to be a bit more like managers, but managers of a team that has the ability to run 24/7.
Konstantin@getKonstantin

I fear the future of work with AI. If you look at where the technology got us with instant messaging, it's clear that the future of work with AI won't be we work less. It will be that we work more, and are expected to contribute prompts at any times to move the agents forward.

English
1
2
12
1.6K